AI agents invoke start_process to trigger actions in Allcanuse. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Starting processes is a direct code/command execution action that can trigger any external operation with unpredictable side effects depending on arguments. An AI agent given this tool could execute malicious, destructive, or unintended commands. This is critical severity due to unrestricted system-level process spawning capability and high blast radius on Windows/Linux systems.
From the tool's definition Tool name 'start_process' indicates execution of arbitrary processes on the system. Server description mentions 'command execution' and 'systematically manage local systems.' No description provided for this specific tool, but context from sibling tools…
Documented attack patterns abuse exactly the kind of access start_process gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Allcanuse, and nothing reaches the server without passing your rules. This is the rule we recommend for start_process:
{
"version": "1",
"default": "deny",
"tools": {
"start_process": {
"limits": [
{
"counter": "start_process_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}start_process stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
start_process. It is categorised as a Execute tool in the Allcanuse MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Allcanuse MCP server in PolicyLayer and add a rule for start_process: 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 Allcanuse. Nothing to install.
start_process is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_process 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 start_process. 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.
start_process is provided by the Allcanuse MCP server (ra1nyxin/allcanuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Allcanuse, 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.
130 Allcanuse tools catalogued and risk-classified — across an index of 43,000+ MCP servers.