Throws on purpose to demonstrate handler exceptions → isError.
AI agents invoke unstable to trigger actions in MCP from Scratch Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool deliberately triggers an exception/error as a demonstration. It executes code that throws intentionally, causing an error state. No data is read, written, or deleted — it purely executes behavior (throwing) to demonstrate error handling. Severity is low because it only throws an exception with no side effects on external data or systems.
From the tool's definition "Throws on purpose to demonstrate handler exceptions → isError"
Documented attack patterns abuse exactly the kind of access unstable gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP from Scratch Server, and nothing reaches the server without passing your rules. This is the rule we recommend for unstable:
{
"version": "1",
"default": "deny",
"tools": {
"unstable": {
"limits": [
{
"counter": "unstable_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} unstable stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Throws on purpose to demonstrate handler exceptions → isError. It is categorised as a Execute tool in the MCP from Scratch Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP from Scratch Server MCP server in PolicyLayer and add a rule for unstable: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches MCP from Scratch Server. Nothing to install.
unstable is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the unstable rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for unstable. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
unstable is provided by the MCP from Scratch Server MCP server (pguso/mcp-from-scratch). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP from Scratch Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 MCP from Scratch Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.