AI agents call export_project to retrieve information from Kanban without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'export_project' strongly implies retrieving and serializing project data for export, which is a Read operation. However, the empty description lowers confidence. In the context of a kanban board MCP server with tools for tracking issues, features, and projects, an export function would typically read and output data without side effects.
From the tool's definition Tool name 'export_project' suggests reading/exporting project data; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access export_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kanban, and nothing reaches the server without passing your rules. This is the rule we recommend for export_project:
{
"version": "1",
"default": "deny",
"tools": {
"export_project": {}
}
}export_project 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_project. It is categorised as a Read tool in the Kanban MCP Server, which means it retrieves data without modifying state.
Register the Kanban 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 Kanban. 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 Kanban MCP server (multidimensionalcats/kanban-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kanban, 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.
45 Kanban tools catalogued and risk-classified — across an index of 43,000+ MCP servers.