Get all attachments for a test plan entry
AI agents call get_attachments_for_plan_entry 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 or queries attachment metadata for a test plan entry without modifying, deleting, or executing any operations. It has no side effects and falls squarely into the Read category. The severity is low because attachment metadata retrieval poses minimal risk—it cannot modify test data, delete resources, or trigger external operations.
From the tool's definition Tool name 'get_attachments_for_plan_entry' and description 'Get all attachments for a test plan entry' indicate a read-only retrieval operation with the verb 'Get'.
Attacks that exploit this kind of access
Get all attachments for a test plan entry. 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_plan_entry: 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_plan_entry 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_plan_entry 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_plan_entry. 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_plan_entry 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 →