Guard proxy errors decoded: 401, 403, 404, 429 and 502 explained
What each Guard proxy response means, from JSON-RPC code -32000 to a bare 401 or 404, and the first thing to check for each.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
What each Guard proxy response means, from JSON-RPC code -32000 to a bare 401 or 404, and the first thing to check for each.
Guard checks MCP requests against rules in priority order and applies the first match. What a rule can match, the three actions, and common mistakes.
Guard rules can inspect tool inputs before a call and mask or cap tool outputs after. The filter types, what they catch, and where regex filters fall short.
Guard logs every MCP request it evaluates, allow, deny or monitor, with scores and rule IDs. What is stored, how long, how to query it, and what is not live.
How a general-purpose AI model is classed as systemic risk, the compute presumption, and the extra duties: testing, incident reports and security.
In May 2024 Google explained odd AI Overviews answers: data voids, satire and forum posts. What it said, which examples were faked, and what changed.
An agent followed injected instructions and acted. In the first hour: stop it, revoke its access, preserve logs, scope the damage, then fix the path.
Research shows custom fine-tuning can erode safety alignment, even with benign data. What it means and how to test a tuned model before shipping.
A fake document hidden inside a normal RAG entry can be treated as a separate result. What ATLAS says about it and how to reduce the exposure.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.