AI agents use create_new_studio_attack to create or update resources in SafeBreach MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SafeBreach MCP Server environment.
The 'create' prefix strongly suggests this tool creates a new attack simulation in the SafeBreach Studio. This is a Write action (creating a new resource). However, triggering attack simulations on a BAS platform could also be considered Execute, as it may launch active simulation operations. With an empty description, confidence is lowered.
From the tool's definition Tool name 'create_new_studio_attack' — 'create' implies creating a new resource; 'studio_attack' aligns with sibling tools like 'get_all_studio_attacks' on a Breach and Attack Simulation platform.
Documented attack patterns abuse exactly the kind of access create_new_studio_attack gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SafeBreach MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_new_studio_attack:
{
"version": "1",
"default": "deny",
"tools": {
"create_new_studio_attack": {
"limits": [
{
"counter": "create_new_studio_attack_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_new_studio_attack 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.
create_new_studio_attack. It is categorised as a Write tool in the SafeBreach MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SafeBreach MCP Server MCP server in PolicyLayer and add a rule for create_new_studio_attack: 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 SafeBreach MCP Server. Nothing to install.
create_new_studio_attack 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_new_studio_attack 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_new_studio_attack. 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_new_studio_attack is provided by the SafeBreach MCP Server MCP server (safebreach/safebreach-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SafeBreach 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.
35 SafeBreach MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.