Get a detailed daily breakdown for a single ad entity (keyword, audience, creative, ad group). Use after audit_account_waste to drill into why a specific entity was flagged — shows day-by-day spend, clicks, impressions and conversions, plus the parent campaign info. Args: - entity_id (number): Th...
AI agents call get_waste_detail to retrieve information from Postgres without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query/retrieval operation with no side effects. It fetches historical analytics data for a specific ad entity with optional filtering by days. The tool supports investigation and analysis but does not modify state, execute external operations, or delete data. Severity is low because misuse would only expose or exfiltrate existing data, not cause operational harm or irreversible changes.
From the tool's definition Tool retrieves and displays detailed daily breakdown data (spend, clicks, impressions, conversions, parent campaign info) for a single ad entity. No creation, modification, deletion, or external execution occurs.
Attacks that exploit this kind of access
Get a detailed daily breakdown for a single ad entity (keyword, audience, creative, ad group). Use after audit_account_waste to drill into why a specific entity was flagged — shows day-by-day spend, clicks, impressions and conversions, plus the parent campaign info. Args: - entity_id (number): The entity ID, from audit_account_waste results - days (number, optional): How many days of history to show. Default 30. Examples: -. It is categorised as a Read tool in the Postgres MCP Server, which means it retrieves data without modifying state.
Register the Postgres MCP server in PolicyLayer and add a rule for get_waste_detail: 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 Postgres. Nothing to install.
get_waste_detail 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_waste_detail 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_waste_detail. 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_waste_detail is provided by the Postgres MCP server (santisanti13/postgres-mcp-server). 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 →