Create a reusable demo script with an intentional bug for debugging walkthroughs.
AI agents use ensure_demo_program to create or update resources in Mcp Debugpy — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Debugpy environment.
This tool creates a new file/script artifact for demonstration purposes. Creating files is a Write operation because it generates new data that is reversible (the file can be edited or deleted separately). The security impact is low since the tool creates a benign demo script with an intentional bug for educational debugging walkthroughs, not arbitrary or malicious code.
From the tool's definition Tool creates a demo script: 'Create a reusable demo script'. The description uses 'Create', indicating data creation rather than querying (Read), execution (Execute), or deletion (Destructive).
Documented attack patterns abuse exactly the kind of access ensure_demo_program gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Debugpy, and nothing reaches the server without passing your rules. This is the rule we recommend for ensure_demo_program:
{
"version": "1",
"default": "deny",
"tools": {
"ensure_demo_program": {
"limits": [
{
"counter": "ensure_demo_program_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ensure_demo_program stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a reusable demo script with an intentional bug for debugging walkthroughs. It is categorised as a Write tool in the Mcp Debugpy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Debugpy MCP server in PolicyLayer and add a rule for ensure_demo_program: 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 Debugpy. Nothing to install.
ensure_demo_program is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ensure_demo_program 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 ensure_demo_program. 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.
ensure_demo_program is provided by the Mcp Debugpy MCP server (markomanninen/mcp-debugpy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Debugpy, 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.
16 Mcp Debugpy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.