Send a signal to a tracked background process (default SIGTERM=15).
AI agents use kill_process to create or update resources in Pwno — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pwno environment.
An AI agent can call kill_process faster than any human can review — one bad instruction and it creates or modifies resources in Pwno by the hundred, each call as confident as the last.
Documented attack patterns abuse exactly the kind of access kill_process gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pwno, and nothing reaches the server without passing your rules. This is the rule we recommend for kill_process:
{
"version": "1",
"default": "deny",
"tools": {
"kill_process": {
"limits": [
{
"counter": "kill_process_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}kill_process 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.
Send a signal to a tracked background process (default SIGTERM=15). It is categorised as a Write tool in the Pwno MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pwno MCP server in PolicyLayer and add a rule for kill_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 Pwno. Nothing to install.
kill_process 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 kill_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 kill_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.
kill_process is provided by the Pwno MCP server (pwno-io/pwno-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 Pwno tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 Pwno tools catalogued and risk-classified — across an index of 42,500+ MCP servers.