Read a UTF-8 text file so agents can inspect generated code before debugging.
AI agents call read_text_file to retrieve information from Mcp Debugpy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves file content for inspection purposes with no side effects. It performs a simple read operation with no capability to modify, execute, or delete data. The low severity reflects the minimal risk from unauthorized file reads in a debugging context where the agent already has access to the debugger infrastructure.
From the tool's definition Tool name is 'read_text_file' and description states 'Read a UTF-8 text file' with purpose to 'inspect generated code before debugging'. The verb 'Read' and action of retrieving file contents without modification are clear indicators of a read-only operation.
Documented attack patterns abuse exactly the kind of access read_text_file 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 read_text_file:
{
"version": "1",
"default": "deny",
"tools": {
"read_text_file": {}
}
}read_text_file is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Read a UTF-8 text file so agents can inspect generated code before debugging. It is categorised as a Read tool in the Mcp Debugpy MCP Server, which means it retrieves data without modifying state.
Register the Mcp Debugpy MCP server in PolicyLayer and add a rule for read_text_file: 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.
read_text_file is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the read_text_file 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 read_text_file. 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.
read_text_file 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.