export_project · Keshro MCP: Risk & Policy

WHAT IT DOES

What export_project does on Keshro MCP

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

WHY IT NEEDS A POLICY

Why export_project needs a policy

Without explicit description, judgment relies on naming convention and server context. 'Export' typically creates or outputs data artifacts, which is Write-category. Severity is high given the 'high-stakes engineering projects' context—unauthorized project export could leak sensitive code, plans, or IP.

From the tool's definition Tool named 'export_project' with empty description. Based on context (Keshro MCP for 'high-stakes engineering projects' with plan/task management), export_project likely serializes or downloads project data, constituting a Write operation (data retrieval with…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

export_project Rate-limited

export_project 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_project": {
      "limits": [
        {
          "counter": "export_project_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 Keshro MCP, so you can run agents against it safely.

FAQ

Questions about export_project

What does the export_project tool do? +

export_project. It is categorised as a Write tool in the Keshro MCP 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_project? +

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

What risk level is export_project? +

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

Can I rate-limit export_project? +

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

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

export_project is provided by the Keshro MCP server (jlewitt1/keshro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.