Stop a persistent BetterDB monitor process that was previously started with start_monitor or --autostart --persist.
Part of the Betterdb server.
Free to start. No card required.
AI agents invoke stop_monitor to trigger processes or run actions in Betterdb. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
stop_monitor can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"stop_monitor": {
"limits": [
{
"counter": "stop_monitor_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Betterdb policy for all 41 tools.
These attack patterns abuse exactly the kind of access stop_monitor gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Stop a persistent BetterDB monitor process that was previously started with start_monitor or --autostart --persist.. It is categorised as a Execute tool in the Betterdb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Betterdb MCP server in PolicyLayer and add a rule for stop_monitor: 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 Betterdb. Nothing to install.
stop_monitor 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 stop_monitor 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 stop_monitor. 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.
stop_monitor is provided by the Betterdb MCP server (@betterdb/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 41 Betterdb 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.