Add an attachment to a test result
AI agents use add_attachment_to_result to create or update resources in TestRail MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TestRail MCP Server environment.
This tool modifies test result data by attaching a file or document to it. While it does not delete or overwrite data (so not Destructive), and does not execute arbitrary code (so not Execute), it does create or add content to an existing resource, making it a Write operation.
From the tool's definition Tool name and description indicate it 'Add[s] an attachment to a test result', creating/adding content to an existing test result entity.
Attacks that exploit this kind of access
Add an attachment to a test result. It is categorised as a Write tool in the TestRail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TestRail MCP Server MCP server in PolicyLayer and add a rule for add_attachment_to_result: 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.
add_attachment_to_result is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_attachment_to_result 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 add_attachment_to_result. 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.
add_attachment_to_result 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 →