AI agents call search 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.
While the description is empty, the name 'search' combined with the server's stated capability for 'semantic search' over kanban items indicates this tool retrieves or queries existing data without modification. No side effects are typical of search operations. Confidence is slightly reduced due to the missing description, but the contextual pattern is clear.
From the tool's definition Tool name 'search' in a kanban board context with an empty description suggests querying/retrieving data. The sibling tools include destructive operations (delete_item, delete_decision, delete_tag), execute operations (advance_status, close_item), and write…
Documented attack patterns abuse exactly the kind of access search 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 search:
{
"version": "1",
"default": "deny",
"tools": {
"search": {}
}
}search 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.
search. 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 search: 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.
search 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 search 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 search. 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.
search 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.