AI agents use create_session to create or update resources in Testdino — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Testdino environment.
An AI agent can call create_session faster than any human can review — one bad instruction and it creates or modifies resources in Testdino by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Create a new exploratory testing session. Requires write permission. mission accepts rich HTML (the high-level charter). assigneeUserId accepts either a User _id (. It is categorised as a Write tool in the Testdino MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Testdino MCP server in PolicyLayer and add a rule for create_session: 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 Testdino. Nothing to install.
create_session 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_session 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_session. 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_session is provided by the Testdino MCP server (testdino-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.