export_data

THE RISK

Low Risk

Why export_data needs a policy

The tool exports (reads/retrieves) customer data records, placing it in the Read category. However, exporting bulk customer data has a high blast radius due to data protection and privacy concerns — a misuse could result in a large-scale data breach. Severity is high because it involves sensitive customer records.

From the tool's definition 'Export customer data records' — retrieves/exports data; 'Blocked by data protection policy' suggests restricted access

Documented attack patterns abuse exactly the kind of access export_data gives an agent:

POLICY

How to control export_data

PolicyLayer is an MCP gateway — it sits between your AI agents and Sdk, and nothing reaches the server without passing your rules. This is the rule we recommend for export_data:

policy.json

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

export_data is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Sdk — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Sdk tools

Execute governance_proxy SidClaw MCP Governance Proxy — wraps any upstream MCP server with policy evaluation, Execute send_email Send an email to a customer. Requires governance approval. Write sidclaw_record Log the outcome of an action that has already executed. Use this when you don Write sidclaw_session_end Close out a client-side session created via sidclaw_session_start. Not Other sidclaw_session_start Generate a client-side session ID for your own bookkeeping. SidClaw does Read search_docs Search the internal knowledge base for documentation and policies. Read sidclaw_policies List active policy rules for the current tenant (or a specific agent). Other sidclaw_approve Wait for a human approval to resolve. Use after sidclaw_evaluate returns

All 10 Sdk tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about export_data

What does the export_data tool do? +

Export customer data records. Blocked by data protection policy. It is categorised as a Read tool in the Sdk MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on export_data? +

Register the Sdk 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 Sdk. 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 Sdk MCP server (@sidclaw/sdk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sdk tool call.

Start from Sdk, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →