AI agents call get_order to retrieve information from Google Ad Manager MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get' prefix is consistently used for retrieval operations. Within a Google Ad Manager context, fetching order details has no side effects and aligns with read-only operations. Even if misused by an agent, retrieving order data presents minimal risk compared to write/execute/destructive operations. Severity remains low as there is no blast radius from mere data retrieval.
From the tool's definition Tool name 'get_order' indicates a retrieval operation. No description provided, but the naming convention and context within an ad management system (alongside create_order, approve_line_item, etc.) strongly suggests this queries/fetches order data without…
Documented attack patterns abuse exactly the kind of access get_order gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Ad Manager MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_order:
{
"version": "1",
"default": "deny",
"tools": {
"get_order": {}
}
}get_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_order. It is categorised as a Read tool in the Google Ad Manager MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Ad Manager MCP Server MCP server in PolicyLayer and add a rule for get_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 Google Ad Manager MCP Server. Nothing to install.
get_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_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_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_order is provided by the Google Ad Manager MCP Server MCP server (matiouscorp/google-ad-manager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Ad Manager MCP Server, 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.
35 Google Ad Manager MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.