Wait for user approval of the plan in the Overture UI. Returns status:
AI agents call get_approval to retrieve information from Overture without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads the current approval status from the Overture UI system. It has no side effects—it does not create, modify, delete, or execute anything. It is a blocking read operation that waits for and returns user authorization state. The actual execution is controlled by other tools in the sibling list (like 'request_plan_update').
From the tool's definition Tool name 'get_approval' and description 'Wait for user approval' indicate a polling/query operation that retrieves approval status from the UI without modifying data or triggering execution.
Documented attack patterns abuse exactly the kind of access get_approval gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Overture, and nothing reaches the server without passing your rules. This is the rule we recommend for get_approval:
{
"version": "1",
"default": "deny",
"tools": {
"get_approval": {}
}
}get_approval 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.
Wait for user approval of the plan in the Overture UI. Returns status:. It is categorised as a Read tool in the Overture MCP Server, which means it retrieves data without modifying state.
Register the Overture MCP server in PolicyLayer and add a rule for get_approval: 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 Overture. Nothing to install.
get_approval 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_approval 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_approval. 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_approval is provided by the Overture MCP server (sixhq/overture). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Overture tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 Overture tools catalogued and risk-classified — across an index of 42,500+ MCP servers.