Adds generated test cases to a test plan linked to a TP card (UserStory, Bug, or Feature).
AI agents use add_test_cases_to_test_plan to create or update resources in Targetprocess — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Targetprocess environment.
An AI agent can call add_test_cases_to_test_plan faster than any human can review — one bad instruction and it creates or modifies resources in Targetprocess by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Adds generated test cases to a test plan linked to a TP card (UserStory, Bug, or Feature). It is categorised as a Write tool in the Targetprocess MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Targetprocess MCP server in PolicyLayer and add a rule for add_test_cases_to_test_plan: 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 Targetprocess. Nothing to install.
add_test_cases_to_test_plan 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_test_cases_to_test_plan 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_test_cases_to_test_plan. 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_test_cases_to_test_plan is provided by the Targetprocess MCP server (targetprocess-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.