Export project as JSON backup
AI agents call export_project to retrieve information from Prowpt MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Exporting a project as a JSON backup is a read operation — it retrieves and serializes project data into a downloadable format without modifying, deleting, or executing anything. No side effects are involved.
From the tool's definition Export project as JSON backup
Attacks that exploit this kind of access
Export project as JSON backup. It is categorised as a Read tool in the Prowpt MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Prowpt MCP Server 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 Prowpt MCP Server. Nothing to install.
export_project is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
export_project is provided by the Prowpt MCP Server MCP server (prowptai/prowpt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →