personal_export

Export vault entries as JSON.

SERVERMCP Framework Personal SOURCEinggerman/mcps

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/inggerman-mcps/personal-export.md

WHAT IT DOES

What personal_export does on MCP Framework Personal

AI agents call personal_export to retrieve information from MCP Framework Personal without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why personal_export is rated Low

The tool reads and exports vault entries (likely sensitive personal data such as passwords, secrets, or credentials stored in a personal vault) as JSON. While it is a read operation with no writes or deletions, the blast radius is high because exporting vault contents could expose all stored secrets or personal data to an attacker or misconfigured agent.

From the tool's definition Export vault entries as JSON

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs personal_export safely

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

personal_export Allowed

personal_export is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "personal_export": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MCP Framework Personal, apply this rule, and every personal_export call is checked against it from then on.

FAQ

Questions about personal_export

What does the personal_export tool do? +

Export vault entries as JSON. It is categorised as a Read tool in the MCP Framework Personal MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on personal_export? +

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

What risk level is personal_export? +

personal_export is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit personal_export? +

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

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

personal_export is provided by the MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Framework Personal, and thousands of servers like it.

This server

All 811 MCP Framework Personal tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →