AI agents call manage_test as a supporting operation in SafeBreach MCP Server workflows.
The description is empty, so the tool's actual behavior cannot be determined from the available information. The name 'manage_test' suggests it may create, update, or control test/simulation configurations on the SafeBreach platform, which could span Write or Execute categories.
From the tool's definition Tool name is 'manage_test' with an empty description. No functional details are provided.
Documented attack patterns abuse exactly the kind of access manage_test 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 manage_test:
{
"version": "1",
"default": "deny",
"tools": {
"manage_test": {
"limits": [
{
"counter": "manage_test_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} manage_test gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
manage_test. It is categorised as a Other tool in the SafeBreach MCP Server MCP Server, which means it performs auxiliary operations.
Register the SafeBreach MCP Server MCP server in PolicyLayer and add a rule for manage_test: 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.
manage_test is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the manage_test 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 manage_test. 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.
manage_test 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.