AI agents call pm_focus to retrieve information from Codecks without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool describes a dashboard view that retrieves and displays categorized cards (blocked, stale, unassigned, suggested). This is a read/query operation with no side effects — it surfaces existing data for PM review without modifying anything.
From the tool's definition PM focus dashboard: blocked, stale, unassigned, and suggested next cards
Attacks that exploit this kind of access
PM focus dashboard: blocked, stale, unassigned, and suggested next cards. It is categorised as a Read tool in the Codecks MCP Server, which means it retrieves data without modifying state.
Register the Codecks MCP server in PolicyLayer and add a rule for pm_focus: 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 Codecks. Nothing to install.
pm_focus 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 pm_focus 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 pm_focus. 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.
pm_focus is provided by the Codecks MCP server (rangogamedev/codecks-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 →