AI agents use get_or_create_section to create or update resources in Testrail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Testrail environment.
The tool resolves a section hierarchy but will create sections that don't exist yet, constituting a reversible write operation. The 'get' path is read-only, but the 'create' path writes new data. Per the rules, the most severe applicable category is Write. Severity is medium since miscreation of sections in TestRail is reversible but could pollute test organization.
From the tool's definition 'get_or_create_section' — the 'create' part implies it may create a new section if one does not exist, modifying TestRail data
Attacks that exploit this kind of access
Resolve a section hierarchy like Auth > Login > Edge Cases,. It is categorised as a Write tool in the Testrail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Testrail MCP server in PolicyLayer and add a rule for get_or_create_section: 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. Nothing to install.
get_or_create_section 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 get_or_create_section 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_or_create_section. 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_or_create_section is provided by the Testrail MCP server (sergey-bl/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 →