attribute_partner_to_deal
Credit a partner on an opportunity. attributionType is STRATEGIC (incremental revenue not won without the partner) or INFLUENCED (facilitation). motion: co_sell, joint_solution, services_delivery, funding, intro, information_sharing, marketplace, reference. MONEY WRITE: dry-run by default (return...
This record as markdown: /tools/adrata-adrata-mcp/attribute-partner-to-deal.md
What attribute_partner_to_deal does on Adrata
AI agents invoke attribute_partner_to_deal 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 attribute_partner_to_deal is rated High
attribute_partner_to_deal 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 attribute_partner_to_deal 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 attribute_partner_to_deal, this is the rule to start with:
attribute_partner_to_deal 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 attribute_partner_to_deal call is checked against it from then on.
Questions about attribute_partner_to_deal
Credit a partner on an opportunity. attributionType is STRATEGIC (incremental revenue not won without the partner) or INFLUENCED (facilitation). motion: co_sell, joint_solution, services_delivery, funding, intro, information_sharing, marketplace, reference. MONEY WRITE: dry-run by default (returns a preview); live execution requires approved:true, a non-empty auditReason, and an idempotencyKey. 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 attribute_partner_to_deal: 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.
attribute_partner_to_deal 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 attribute_partner_to_deal 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 attribute_partner_to_deal. 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.
attribute_partner_to_deal 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