Creates a new test session context for stateful testing workflows.
AI agents use create_test_session_context to create or update resources in MockLoop MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MockLoop MCP Server environment.
This tool creates new persistent state (a test session context) rather than merely reading data, placing it in the Write category. It is not Destructive (no deletion), Financial, or Execute (does not directly run code/commands, though it enables other tools to do so).
From the tool's definition create_test_session_context creates a new test session context, which establishes or modifies the state of testing workflows.
Documented attack patterns abuse exactly the kind of access create_test_session_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MockLoop MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_test_session_context:
{
"version": "1",
"default": "deny",
"tools": {
"create_test_session_context": {
"limits": [
{
"counter": "create_test_session_context_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_test_session_context stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Creates a new test session context for stateful testing workflows. It is categorised as a Write tool in the MockLoop MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MockLoop MCP Server MCP server in PolicyLayer and add a rule for create_test_session_context: 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 MockLoop MCP Server. Nothing to install.
create_test_session_context 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_session_context 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_session_context. 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_session_context is provided by the MockLoop MCP Server MCP server (mockloop/mockloop-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MockLoop MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
30 MockLoop MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.