Deactivate your agent identity. Soft-deletes: removes from channels, disables webhooks. Messages expire per TTL.
Risk signalsHandles credentials or secrets (api_key)
Part of the Voidly server.
Free to start. No card required.
AI agents call agent_deactivate to retrieve information from Voidly without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though agent_deactivate only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"agent_deactivate": {}
}
}See the full Voidly policy for all 84 tools.
These attack patterns abuse exactly the kind of access agent_deactivate gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Deactivate your agent identity. Soft-deletes: removes from channels, disables webhooks. Messages expire per TTL.. It is categorised as a Read tool in the Voidly MCP Server, which means it retrieves data without modifying state.
Register the Voidly MCP server in PolicyLayer and add a rule for agent_deactivate: 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 Voidly. Nothing to install.
agent_deactivate is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the agent_deactivate 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 agent_deactivate. 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.
agent_deactivate is provided by the Voidly MCP server (@voidly/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 84 Voidly tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.