Get merchant order by ID
AI agents call get_merchant_order to retrieve information from Mcp Ap2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves merchant order information without modifying, deleting, or executing any operations. It is a simple query/fetch operation that returns existing data. While the server handles financial contexts (AP2 is Google's payment protocol), this specific tool does not move money, create obligations, or alter state—it merely reads order details by identifier.
From the tool's definition Tool name 'get_merchant_order' with description 'Get merchant order by ID' indicates a retrieval operation. The verb 'Get' and the absence of modification, deletion, or financial transaction language confirm read-only behavior.
Documented attack patterns abuse exactly the kind of access get_merchant_order gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for get_merchant_order:
{
"version": "1",
"default": "deny",
"tools": {
"get_merchant_order": {}
}
}get_merchant_order is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get merchant order by ID. It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for get_merchant_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 Mcp Ap2. Nothing to install.
get_merchant_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 get_merchant_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 get_merchant_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.
get_merchant_order is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.