Get all generated code blocks from a test file
AI agents call get_generated_code to retrieve information from Testing without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns data (generated code blocks) without side effects. It does not execute, modify, delete, or create code — it only retrieves existing information from a test file. This is a straightforward Read operation with low severity, as exposure carries minimal risk: an agent can only view code, not alter it or trigger unintended actions.
From the tool's definition Tool retrieves 'all generated code blocks from a test file' — a read operation with no modification, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access get_generated_code gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Testing, and nothing reaches the server without passing your rules. This is the rule we recommend for get_generated_code:
{
"version": "1",
"default": "deny",
"tools": {
"get_generated_code": {}
}
}get_generated_code 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.
Get all generated code blocks from a test file. It is categorised as a Read tool in the Testing MCP Server, which means it retrieves data without modifying state.
Register the Testing MCP server in PolicyLayer and add a rule for get_generated_code: 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 Testing. Nothing to install.
get_generated_code 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 get_generated_code 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 get_generated_code. 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.
get_generated_code is provided by the Testing MCP server (mcpland/testing-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Testing, 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.
5 Testing tools catalogued and risk-classified — across an index of 43,000+ MCP servers.