crm_media_rename

Rename a file or folder in the CRM media library.

SERVER0nmcp SOURCE0nmcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-0nork-0nmcp/crm-media-rename.md

WHAT IT DOES

What crm_media_rename does on 0nmcp

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

RISK

Why crm_media_rename is rated Medium

Renaming files/folders is a write operation that modifies data structure reversibly. It is not destructive (data not deleted), not financial, and not execute (no code/command execution). Severity is medium because renaming in a CRM media library could cause confusion if done incorrectly (breaking references, losing discoverability), but the change is reversible via another rename operation.

From the tool's definition Tool name contains 'rename' and description states 'Rename a file or folder in the CRM media library' — rename is a reversible modification operation that alters metadata/naming without deleting data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs crm_media_rename safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 0nmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crm_media_rename, this is the rule to start with:

crm_media_rename Rate-limited

crm_media_rename 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": {
    "crm_media_rename": {
      "limits": [
        {
          "counter": "crm_media_rename_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 0nmcp, apply this rule, and every crm_media_rename call is checked against it from then on.

FAQ

Questions about crm_media_rename

What does the crm_media_rename tool do? +

Rename a file or folder in the CRM media library. It is categorised as a Write tool in the 0nmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on crm_media_rename? +

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

What risk level is crm_media_rename? +

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

Can I rate-limit crm_media_rename? +

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

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

crm_media_rename is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 0n, and thousands of servers like it.

This server

All 218 0n tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →