renameDocumentOrNotebookEntry · RSpace MCP Server MCP

WHAT IT DOES

What renameDocumentOrNotebookEntry does on RSpace MCP Server

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

WHY IT NEEDS A POLICY

Why renameDocumentOrNotebookEntry needs a policy

Renaming is a write operation that modifies document/notebook entry metadata but does not delete, destroy, or create new data irreversibly. It is reversible (can be renamed back) and has no financial implications. The blast radius is medium because bulk renaming by an agent could cause confusion or organizational problems, but the action itself is non-destructive and easily correctable.

From the tool's definition The tool "renameDocumentOrNotebookEntry" performs a metadata modification operation. The description states it "Renames a document or notebook entry", which is a reversible change to an existing resource's properties.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

renameDocumentOrNotebookEntry Rate-limited

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

FAQ

Questions about renameDocumentOrNotebookEntry

What does the renameDocumentOrNotebookEntry tool do? +

Renames a document or notebook entry. It is categorised as a Write tool in the RSpace 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 renameDocumentOrNotebookEntry? +

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

What risk level is renameDocumentOrNotebookEntry? +

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

Can I rate-limit renameDocumentOrNotebookEntry? +

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

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

renameDocumentOrNotebookEntry is provided by the RSpace MCP Server MCP server (richarda23/rspace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.