AI agents call get_card_details to retrieve information from Framedeck without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns data about a card. It performs no create, update, delete, or execution operations. The blast radius of misuse is minimal — an agent could only over-retrieve data or access information it shouldn't, but cannot modify or destroy anything. This is a classic Read operation.
From the tool's definition Tool name 'get_card_details' and description states it retrieves 'full details of a card including comments, checklists, attachments, and labels' — purely informational retrieval with no modifications or side effects.
Attacks that exploit this kind of access
Get full details of a card including comments, checklists, attachments, and labels. It is categorised as a Read tool in the Framedeck MCP Server, which means it retrieves data without modifying state.
Register the Framedeck MCP server in PolicyLayer and add a rule for get_card_details: 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 Framedeck. Nothing to install.
get_card_details 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_card_details 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_card_details. 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_card_details is provided by the Framedeck MCP server (lukaris/framedeck-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 →