build_pursuit_command_center
Build or refresh Adrata’s persistent, evidence-linked Pursuit command center for one enterprise account. Composes the active opportunity, structured MEDDPICC, buyer room and path to power, deal health and forecast risk, triggers, one recommended Give/Get move, and reviewable email/cadence proposa...
This record as markdown: /tools/adrata-adrata-mcp/build-pursuit-command-center.md
What build_pursuit_command_center does on Adrata
AI agents invoke build_pursuit_command_center to trigger actions in Adrata. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why build_pursuit_command_center is rated High
build_pursuit_command_center triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs build_pursuit_command_center safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adrata, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For build_pursuit_command_center, this is the rule to start with:
build_pursuit_command_center stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Adrata, apply this rule, and every build_pursuit_command_center call is checked against it from then on.
Questions about build_pursuit_command_center
Build or refresh Adrata’s persistent, evidence-linked Pursuit command center for one enterprise account. Composes the active opportunity, structured MEDDPICC, buyer room and path to power, deal health and forecast risk, triggers, one recommended Give/Get move, and reviewable email/cadence proposals. Preview is non-mutating by default. Persisting the artifact or cadence requires the server-issued confirmation flow, an audit reason, and idempotent governed execution. It is categorised as a Execute tool in the Adrata MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Adrata MCP server in PolicyLayer and add a rule for build_pursuit_command_center: 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 Adrata. Nothing to install.
build_pursuit_command_center is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the build_pursuit_command_center 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 build_pursuit_command_center. 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.
build_pursuit_command_center is provided by the Adrata MCP server (@adrata/adrata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adrata, and thousands of servers like it.
Across the catalogue