Add multiple test results
AI agents use add_bulk_results 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 creates or modifies test result data in bulk, which is a Write operation. It has medium severity because bulk modifications could affect test tracking and reporting, but the operation is reversible (results can be updated or corrected). The blast radius is limited to test result data within TestRail rather than system-wide impact.
From the tool's definition Tool name 'add_bulk_results' and description 'Add multiple test results' indicate creation/modification of test result records in TestRail without deletion or irreversible destruction.
Attacks that exploit this kind of access
Add multiple test results. 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_bulk_results: 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_bulk_results 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_bulk_results 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_bulk_results. 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_bulk_results is provided by the TestRail MCP Server MCP server (samuelvinay91/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 →