AI agents call get_status_history 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.
This tool retrieves historical status information from the kanban board system. It performs a query operation with no side effects—it does not create, modify, delete, or execute any operations. Historical data retrieval is a standard Read category operation. Even though the description is empty, the function name itself provides sufficient evidence of its read-only nature.
From the tool's definition Tool name 'get_status_history' indicates retrieval of historical status data. The verb 'get' is a read operation. No description provided, but the name strongly suggests querying/retrieving past status information without modification.
Documented attack patterns abuse exactly the kind of access get_status_history 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 get_status_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_status_history": {}
}
}get_status_history 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.
get_status_history. 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 get_status_history: 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.
get_status_history 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 get_status_history 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 get_status_history. 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.
get_status_history 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.