export_data

Export memory.db table data to file

SERVERProject Guardian MCP SOURCE1999azzar/project-guardian-mcp-server

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/1999azzar-project-guardian-mcp-server/export-data.md

WHAT IT DOES

What export_data does on Project Guardian MCP

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

RISK

Why export_data is rated Low

The tool reads data from the memory database and writes it to a file. The primary action is reading/exporting existing data rather than modifying the database itself. However, it does write a file to the filesystem, which could have implications if sensitive data is exported to an unintended location.

From the tool's definition Export memory.db table data to file

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs export_data safely

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

export_data Allowed

export_data 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": {
    "export_data": {}
  }
}

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

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

FAQ

Questions about export_data

What does the export_data tool do? +

Export memory.db table data to file. It is categorised as a Read tool in the Project Guardian MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on export_data? +

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

What risk level is export_data? +

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

Can I rate-limit export_data? +

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

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

export_data is provided by the Project Guardian MCP server (1999azzar/project-guardian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Project Guardian, and thousands of servers like it.

This server

All 38 Project Guardian tools →

Across the catalogue

get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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