Clareo

45 tools. 23 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated:

23 can modify or destroy data
22 read-only
45 tools total
Read (22) Write / Execute (20) Destructive / Financial (3)

Financial operations (transfer_task) can move real money. An agent caught in a loop could drain accounts before anyone notices.

Destructive tools (adjust_time, delete_task) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (add_checklist_item, complete_task, create_agenda_event) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (start_task) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

One command. Full control.

Intercept sits between your agent and Clareo. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.

npx -y @policylayer/intercept scan -- npx -y @clareo/clareo-mcp
Scans every tool. Generates a policy. Starts enforcing.
Works with Claude Code · Cursor · Claude Desktop · Windsurf · any MCP client
Block financial tools by default
transfer_task:
  rules:
    - action: deny

Financial tools should be explicitly enabled per use case, not open by default.

Deny destructive operations
adjust_time:
  rules:
    - action: deny

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
add_checklist_item:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
get_agency_report:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Can an AI agent move money through the Clareo MCP server? +

Yes. The Clareo server exposes 1 financial tools including transfer_task. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. Intercept lets you block financial tools by default or set per-tool rate limits.

Can an AI agent delete data through the Clareo MCP server? +

Yes. The Clareo server exposes 2 destructive tools including adjust_time, delete_task. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Clareo? +

The Clareo server has 19 write tools including add_checklist_item, complete_task, create_agenda_event. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

How many tools does the Clareo MCP server expose? +

45 tools across 5 categories: Destructive, Execute, Financial, Read, Write. 22 are read-only. 23 can modify, create, or delete data.

How do I add Intercept to my Clareo setup? +

One line change. Instead of running the Clareo server directly, prefix it with Intercept: intercept -c clareo.yaml -- npx -y @@clareo/clareo-mcp. Download a pre-built policy from policylayer.com/policies/clareo and adjust the limits to match your use case.

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

policylayer/intercept

Control every MCP tool call
your agent makes.

Set budgets, approvals, and hard limits across MCP servers.

npx -y @policylayer/intercept init
Protect your agent in 30 seconds. Scans your MCP config and generates enforcement policies for every server.
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.