AI agents call export-chart to retrieve information from PI API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Exporting a chart reads/retrieves existing chart data and converts it to a different format (e.g., PNG, PDF, CSV). This is fundamentally a read operation with no side effects on the server data. Severity is low as it only exposes existing chart data.
From the tool's definition Export a chart in various formats
Documented attack patterns abuse exactly the kind of access export-chart gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PI API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for export-chart:
{
"version": "1",
"default": "deny",
"tools": {
"export-chart": {}
}
} export-chart is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Export a chart in various formats. It is categorised as a Read tool in the PI API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PI API MCP Server MCP server in PolicyLayer and add a rule for export-chart: 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 PI API MCP Server. Nothing to install.
export-chart 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-chart 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-chart. 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-chart is provided by the PI API MCP Server MCP server (mingzilla/pi-api-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PI API MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 PI API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.