create_external_document · MCP Personal Assistant MCP

WHAT IT DOES

What create_external_document does on MCP Personal Assistant

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

WHY IT NEEDS A POLICY

Why create_external_document needs a policy

This tool creates new data (a reference/link to an external document) within the system, making it a Write operation. It is not Read (no retrieval only), not Execute (no code/command execution), not Destructive (reversible), and not Financial.

From the tool's definition Tool name 'create_external_document' and description 'Create a reference to an external document' indicate data creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_external_document Rate-limited

create_external_document 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": {
    "create_external_document": {
      "limits": [
        {
          "counter": "create_external_document_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 Personal Assistant, so you can run agents against it safely.

FAQ

Questions about create_external_document

What does the create_external_document tool do? +

Create a reference to an external document (e.g., cloud storage link). It is categorised as a Write tool in the MCP Personal Assistant MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_external_document? +

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

What risk level is create_external_document? +

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

Can I rate-limit create_external_document? +

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

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

create_external_document is provided by the MCP Personal Assistant MCP server (swapnilsurdi/mcp-pa). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

create_external_document is one line of MCP Personal Assistant'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 →