Approve or reject recommendations, optionally creating tasks.
AI agents use adopt_advisory_recommendations to create or update resources in Quarterback — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Quarterback environment.
This tool modifies the state of recommendations (approving or rejecting them) and can create new tasks as a side effect. Both actions are reversible write operations — no data is permanently destroyed, no code is executed, and no financial transactions occur. The blast radius is medium because an AI agent could approve unintended recommendations or create spurious tasks across projects.
From the tool's definition Approve or reject recommendations, optionally creating tasks
Attacks that exploit this kind of access
Approve or reject recommendations, optionally creating tasks. It is categorised as a Write tool in the Quarterback MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Quarterback MCP server in PolicyLayer and add a rule for adopt_advisory_recommendations: 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 Quarterback. Nothing to install.
adopt_advisory_recommendations is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the adopt_advisory_recommendations 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 adopt_advisory_recommendations. 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.
adopt_advisory_recommendations is provided by the Quarterback MCP server (bobbyrgoldsmith/quarterback). 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 →