rename_category_tool · MCP Feed Reader MCP: Risk & Policy

WHAT IT DOES

What rename_category_tool does on MCP Feed Reader

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

WHY IT NEEDS A POLICY

Why rename_category_tool needs a policy

Renaming a category modifies stored data but is fully reversible—the original category name can be restored by renaming back. This is a Write operation, not Destructive. The impact is limited to organizing feed subscriptions with no data loss or external side effects. Severity is low due to confined scope and reversibility.

From the tool's definition Tool name is 'rename_category_tool' and description states 'Rename a category.' This is a reversible metadata modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_category_tool Rate-limited

rename_category_tool 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": {
    "rename_category_tool": {
      "limits": [
        {
          "counter": "rename_category_tool_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 MCP Feed Reader, so you can run agents against it safely.

FAQ

Questions about rename_category_tool

What does the rename_category_tool tool do? +

Rename a category. It is categorised as a Write tool in the MCP Feed Reader MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename_category_tool? +

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

What risk level is rename_category_tool? +

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

Can I rate-limit rename_category_tool? +

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

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

rename_category_tool is provided by the MCP Feed Reader MCP server (pypi:mcp-feed-reader-crunchtools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

rename_category_tool is one line of MCP Feed Reader's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →