AI agents use testmo_upload_case_attachments to create or update resources in Testmo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Testmo environment.
Uploading attachments modifies test case records by adding files, which is a Write operation. Severity is medium because it creates new data (files) that could bloat storage or introduce unwanted content, but the effect is reversible (attachments can be removed). Confidence is 0.75 rather than higher because the description is empty, making it impossible to verify exact behavior, parameters, or constraints.
From the tool's definition Tool name indicates 'upload' action with 'attachments', which creates or adds file data to test cases. No destructive language (delete, drop, purge) or financial operations present.
Attacks that exploit this kind of access
testmo_upload_case_attachments. It is categorised as a Write tool in the Testmo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Testmo MCP server in PolicyLayer and add a rule for testmo_upload_case_attachments: 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 Testmo. Nothing to install.
testmo_upload_case_attachments 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 testmo_upload_case_attachments 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 testmo_upload_case_attachments. 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.
testmo_upload_case_attachments is provided by the Testmo MCP server (strelec00/testmo-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 →