list_partner_attributions
List every partner attribution on an opportunity (who drove strategic vs influenced revenue). The API route has no pagination; limit/offset are applied client-side by this tool (default cap ${CLIENT_PAGE_CAP} rows).
This record as markdown: /tools/adrata-adrata-mcp/list-partner-attributions.md
What list_partner_attributions does on Adrata
AI agents call list_partner_attributions to retrieve information from Adrata without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_partner_attributions is rated Low
Even though list_partner_attributions only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs list_partner_attributions 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 list_partner_attributions, this is the rule to start with:
list_partner_attributions is read-only, so it stays allowed. 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 list_partner_attributions call is checked against it from then on.
Questions about list_partner_attributions
List every partner attribution on an opportunity (who drove strategic vs influenced revenue). The API route has no pagination; limit/offset are applied client-side by this tool (default cap ${CLIENT_PAGE_CAP} rows). It is categorised as a Read tool in the Adrata MCP Server, which means it retrieves data without modifying state.
Register the Adrata MCP server in PolicyLayer and add a rule for list_partner_attributions: 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.
list_partner_attributions 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 list_partner_attributions 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 list_partner_attributions. 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.
list_partner_attributions 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.
This server
Across the catalogue