Get a specific card order by ID
AI agents call pex_get_card_order to retrieve information from PEX MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool merely retrieves information about a card order by its ID. It does not create, modify, delete, or trigger any external operations. The action is purely informational and carries no risk of unintended side effects. No financial transactions are initiated, and no data is altered. This is a straightforward read operation with minimal security risk.
From the tool's definition Tool name 'pex_get_card_order' with description 'Get a specific card order by ID' indicates a retrieval operation with no side effects. The verb 'get' and the read-only nature of querying an existing card order confirm this is a data retrieval function.
Attacks that exploit this kind of access
Get a specific card order by ID. It is categorised as a Read tool in the PEX MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PEX MCP Server MCP server in PolicyLayer and add a rule for pex_get_card_order: 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 PEX MCP Server. Nothing to install.
pex_get_card_order 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 pex_get_card_order 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 pex_get_card_order. 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.
pex_get_card_order is provided by the PEX MCP Server MCP server (pexcard/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 →