auto_tag_content · Inkwell MCP Server MCP: Risk & Policy

WHAT IT DOES

What auto_tag_content does on Inkwell MCP Server

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

WHY IT NEEDS A POLICY

Why auto_tag_content needs a policy

The primary function is AI-based analysis (Read/Execute), but the tool optionally persists the resulting tags to KV metadata and D1 index, making it a Write operation when that option is used. Since the most severe applicable category applies and writing to storage is reversible, this is classified as Write with medium severity — misuse could corrupt content metadata across the site.

From the tool's definition 'Optionally persists tags to KV meta and D1 index' — the tool can write/update metadata in KV store and D1 database index

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

auto_tag_content Rate-limited

auto_tag_content 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": {
    "auto_tag_content": {
      "limits": [
        {
          "counter": "auto_tag_content_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 Inkwell MCP Server, so you can run agents against it safely.

FAQ

Questions about auto_tag_content

What does the auto_tag_content tool do? +

Use Workers AI to analyze content and suggest relevant topic tags. Provide a slug (looks up from KV) or raw text. Optionally persists tags to KV meta and D1 index. It is categorised as a Write tool in the Inkwell MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on auto_tag_content? +

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

What risk level is auto_tag_content? +

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

Can I rate-limit auto_tag_content? +

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

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

auto_tag_content is provided by the Inkwell MCP Server MCP server (mumega-com/inkwell). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.