AI agents use create_test_suite to create or update resources in Tuskr — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tuskr environment.
This tool creates a new test suite, which is a reversible write operation (suites can typically be deleted or archived in test management systems). It does not execute arbitrary code, delete data, move money, or trigger external side effects beyond the test management system itself. The 'main folder' structure suggests organizational metadata creation.
From the tool's definition Tool description states 'Create a Tuskr test suite (main folder)' — the verb 'Create' and the action of establishing a new organizational container for test cases indicates irreversible data creation.
Attacks that exploit this kind of access
Create a Tuskr test suite (main folder). It is categorised as a Write tool in the Tuskr MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tuskr MCP server in PolicyLayer and add a rule for create_test_suite: 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 Tuskr. Nothing to install.
create_test_suite 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 create_test_suite 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 create_test_suite. 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.
create_test_suite is provided by the Tuskr MCP server (zapkid/tuskr-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 →