Interactive setup wizard for new Quarterback installations.
AI agents use setup_quarterback 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 creates or modifies configuration data during system initialization, which falls under Write category. The severity is high because a misconfigured setup could affect all downstream task prioritization and orchestration operations across multiple projects.
From the tool's definition Tool name 'setup_quarterback' with description 'Interactive setup wizard for new Quarterback installations' indicates initial configuration and establishment of system parameters.
Attacks that exploit this kind of access
Interactive setup wizard for new Quarterback installations. 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 setup_quarterback: 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.
setup_quarterback 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 setup_quarterback 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 setup_quarterback. 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.
setup_quarterback 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 →