Search for cards across all boards in a project
AI agents call planka_search_cards_in_project to retrieve information from Planka MCP Server for Claude without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data (searching for cards) without producing side effects or modifying state. It is a read-only operation that fits the 'Read' category for information retrieval tools.
From the tool's definition Tool name includes 'search' and description states 'Search for cards across all boards in a project' with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search for cards across all boards in a project. It is categorised as a Read tool in the Planka MCP Server for Claude MCP Server, which means it retrieves data without modifying state.
Register the Planka MCP Server for Claude MCP server in PolicyLayer and add a rule for planka_search_cards_in_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 Planka MCP Server for Claude. Nothing to install.
planka_search_cards_in_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 planka_search_cards_in_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 planka_search_cards_in_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.
planka_search_cards_in_project is provided by the Planka MCP Server for Claude MCP server (nextheberg/planka-mcp-server-for-claude). 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 →