AI agents call get_workflow_preferences 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.
This tool retrieves stored preference data without modifying, executing, or deleting anything. It is a straightforward read operation that queries existing configuration or preference state. The note that 'no auth needed' does not elevate the risk category, only the accessibility.
From the tool's definition Tool name is 'get_workflow_preferences' with verb 'get', and description states it 'Load[s] user workflow preferences from past sessions' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
Load user workflow preferences from past sessions. No auth needed. 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 get_workflow_preferences: 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.
get_workflow_preferences 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_workflow_preferences 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_workflow_preferences. 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_workflow_preferences 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 →