Simulate the budget impact of pausing one or more entities, WITHOUT making any changes. Calculates how much daily/monthly spend would be freed up if the given entities were paused, based on their average daily spend over the last N days. Use this BEFORE calling pause_entity to show the projected ...
AI agents call simulate_reallocation 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 tool retrieves and analyzes historical spend data to project hypothetical outcomes, but does not create, modify, delete, or execute any actual changes. It is purely informational and used for planning purposes before calling pause_entity. This is a classic Read operation with no side effects.
From the tool's definition Tool description explicitly states 'WITHOUT making any changes' and 'Calculates how much daily/monthly spend would be freed up if the given entities were paused'.
Attacks that exploit this kind of access
Simulate the budget impact of pausing one or more entities, WITHOUT making any changes. Calculates how much daily/monthly spend would be freed up if the given entities were paused, based on their average daily spend over the last N days. Use this BEFORE calling pause_entity to show the projected impact. Args: - entity_ids (array of numbers): Entities to simulate pausing - days (number, optional): Lookback window for averaging spend. 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 simulate_reallocation: 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.
simulate_reallocation 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 simulate_reallocation 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 simulate_reallocation. 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.
simulate_reallocation 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 →