cache_set · Dobbe MCP: Risk & Policy

WHAT IT DOES

What cache_set does on Dobbe

AI agents use cache_set to create or update resources in Dobbe — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dobbe environment.

WHY IT NEEDS A POLICY

Why cache_set needs a policy

cache_set creates or modifies cached data, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read (Read).

From the tool's definition Tool description states 'Cache a result for future use', which involves creating and storing data in a cache system. Combined with server context involving 'Automates DevOps workflows' and sibling tools managing pipelines, this tool modifies cached state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cache_set Rate-limited

cache_set 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cache_set": {
      "limits": [
        {
          "counter": "cache_set_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Dobbe, so you can run agents against it safely.

FAQ

Questions about cache_set

What does the cache_set tool do? +

Cache a result for future use (default TTL: 4 hours). It is categorised as a Write tool in the Dobbe MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on cache_set? +

Register the Dobbe MCP server in PolicyLayer and add a rule for cache_set: 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 Dobbe. Nothing to install.

What risk level is cache_set? +

cache_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cache_set? +

Yes. Add a rate_limit block to the cache_set 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.

How do I block cache_set completely? +

Set action: deny in the PolicyLayer policy for cache_set. 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.

What MCP server provides cache_set? +

cache_set is provided by the Dobbe MCP server (nareshnavinash/dobbe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.