export_local_documents

WHAT IT DOES

What export_local_documents does on Unified Salesforce Documentation MCP Server

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

WHY IT NEEDS A POLICY

Why export_local_documents needs a policy

The tool writes a file to the local filesystem by concatenating documentation pages into a Markdown file. This is a Write operation (creating/writing a file). It is not purely Read because it produces a new file artifact on disk. Misuse could overwrite existing files or produce large files, hence medium severity.

From the tool's definition Export all matching offline documentation pages concatenated into a single Markdown file on your local machine

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

export_local_documents Rate-limited

export_local_documents 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": {
    "export_local_documents": {
      "limits": [
        {
          "counter": "export_local_documents_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 Unified Salesforce Documentation MCP Server, so you can run agents against it safely.

FAQ

Questions about export_local_documents

What does the export_local_documents tool do? +

Export all matching offline documentation pages concatenated into a single Markdown file on your local machine. It is categorised as a Write tool in the Unified Salesforce Documentation 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 export_local_documents? +

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

What risk level is export_local_documents? +

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

Can I rate-limit export_local_documents? +

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

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

export_local_documents is provided by the Unified Salesforce Documentation MCP Server MCP server (tmtrevisan/unified-sf-docs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.