Get all attachments for a test case
AI agents call get_attachments_for_case to retrieve information from TestRail MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves attachment metadata/files associated with a test case without creating, modifying, deleting, or executing anything. It is a straightforward read operation on TestRail data. The blast radius is minimal — worst case an AI agent could enumerate attachments it shouldn't see, but this is a read-only information disclosure risk rather than a destructive or executable risk.
From the tool's definition Tool name is 'get_attachments_for_case' and description states 'Get all attachments for a test case' — purely retrieval operation with no modification or execution.
Attacks that exploit this kind of access
Get all attachments for a test case. It is categorised as a Read tool in the TestRail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TestRail MCP Server MCP server in PolicyLayer and add a rule for get_attachments_for_case: 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 TestRail MCP Server. Nothing to install.
get_attachments_for_case 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_attachments_for_case 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_attachments_for_case. 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_attachments_for_case is provided by the TestRail MCP Server MCP server (tenbarrel6/testrail-mcp). 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 →