Retrieve the test execution logs. Test are meant to run continuously and log their output to a file.
AI agents call get_test_execution_logs to retrieve information from Coder Toolbox MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and retrieves existing test execution log data from files. It does not modify, delete, execute, or create any data. The use of 'Retrieve' clearly indicates a read-only operation. The low severity reflects the minimal risk—logs are typically informational and non-sensitive in most development contexts, though sensitivity could vary based on what the logs contain.
From the tool's definition The tool description explicitly states 'Retrieve the test execution logs', which is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Retrieve the test execution logs. Test are meant to run continuously and log their output to a file. It is categorised as a Read tool in the Coder Toolbox MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Coder Toolbox MCP Server MCP server in PolicyLayer and add a rule for get_test_execution_logs: 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 Coder Toolbox MCP Server. Nothing to install.
get_test_execution_logs 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_test_execution_logs 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_test_execution_logs. 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_test_execution_logs is provided by the Coder Toolbox MCP Server MCP server (lamemind/coder-toolbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →