Deception: canary tokens, honeyport listeners, trigger detection, canary management
Part of the Defense MCP server.
Free to start. No card required.
AI agents use honeypot_manage to create or modify resources in Defense MCP. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call honeypot_manage repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Defense MCP.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"honeypot_manage": {
"limits": [
{
"counter": "honeypot_manage_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Defense MCP policy for all 31 tools.
These attack patterns abuse exactly the kind of access honeypot_manage gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Deception: canary tokens, honeyport listeners, trigger detection, canary management. It is categorised as a Write tool in the Defense MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Defense MCP server in PolicyLayer and add a rule for honeypot_manage: 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 Defense MCP. Nothing to install.
honeypot_manage 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 honeypot_manage 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 honeypot_manage. 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.
honeypot_manage is provided by the Defense MCP server (bottobot/defense-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 31 Defense MCP 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.