cache_design_with_source · Kiln MCP: Risk & Policy

WHAT IT DOES

What cache_design_with_source does on Kiln

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

WHY IT NEEDS A POLICY

Why cache_design_with_source needs a policy

The name implies writing data to a cache (storing a design with its source), which is a Write operation. However, since the description is empty and uninformative, confidence is low. Based on naming convention alone, this appears to create or update cached design data, which is reversible and classifies as Write.

From the tool's definition Tool name 'cache_design_with_source' suggests storing/writing design data with source information. Description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cache_design_with_source Rate-limited

cache_design_with_source 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_design_with_source": {
      "limits": [
        {
          "counter": "cache_design_with_source_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 Kiln, so you can run agents against it safely.

FAQ

Questions about cache_design_with_source

What does the cache_design_with_source tool do? +

cache_design_with_source. It is categorised as a Write tool in the Kiln 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_design_with_source? +

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

What risk level is cache_design_with_source? +

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

Can I rate-limit cache_design_with_source? +

Yes. Add a rate_limit block to the cache_design_with_source 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_design_with_source completely? +

Set action: deny in the PolicyLayer policy for cache_design_with_source. 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_design_with_source? +

cache_design_with_source is provided by the Kiln MCP server (codeofaxel/Kiln). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.