crow_export_blog

THE RISK

Low Risk

Why crow_export_blog needs a policy

This tool reads/exports already-published post data into markdown format. It does not create, modify, or delete data — it is a read/export operation. Severity is low as it only retrieves existing published content.

From the tool's definition Export published posts as Hugo or Jekyll-compatible markdown files

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

POLICY

How to control crow_export_blog

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

policy.json

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

crow_export_blog 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 Crow — 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 Crow tools

Financial crow_tax_prepare_from_documents One-step tax return preparation: creates a return from ALL confirmed documents uploaded th Financial crow_actual_create_transaction Create a new transaction. Amount in cents (negative = expense, positive = income). Financial crow_tax_set_capital_gains Add Schedule D capital gain/loss transactions. Destructive caddy_remove_site Remove a site block from the Caddyfile (matched by address) and reload Caddy. Destructive Destructive crow_bookstack_delete Delete a page or chapter from BookStack (irreversible) Destructive crow_campaign_delete Delete a campaign and all its posts. Requires confirmation. Destructive crow_crosspost_cancel Cancel a queued cross-post before its scheduled_at fires. Idempotent — cancelling an alrea Destructive crow_delete_context_section Delete a custom crow.md section. Protected sections cannot be deleted — only disabled. Sco

All 576 Crow 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 crow_export_blog

What does the crow_export_blog tool do? +

Export published posts as Hugo or Jekyll-compatible markdown files. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on crow_export_blog? +

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

What risk level is crow_export_blog? +

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

Can I rate-limit crow_export_blog? +

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

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

crow_export_blog is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Crow tool call.

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

CHECK YOUR STACK →