Get status transition rules for cards. Call this BEFORE attempting status updates to understand requirements.
AI agents call get_transition_rules to retrieve information from Planning Game without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns configuration data about allowed status transitions for cards. It does not modify, delete, or execute any operations — it simply retrieves rules. This is a classic Read operation with minimal risk; an agent calling it will only obtain information to inform subsequent decisions.
From the tool's definition Tool name is 'get_transition_rules' and description states 'Get status transition rules' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get status transition rules for cards. Call this BEFORE attempting status updates to understand requirements. It is categorised as a Read tool in the Planning Game MCP Server, which means it retrieves data without modifying state.
Register the Planning Game MCP server in PolicyLayer and add a rule for get_transition_rules: 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 Planning Game. Nothing to install.
get_transition_rules 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_transition_rules 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_transition_rules. 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_transition_rules is provided by the Planning Game MCP server (planning-game-mcp). 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 →