New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

approve_partner_attribution

Approve a partner attribution (finance/ops sign-off). Writes an immutable audit row so strategic revenue stays defensible. MONEY WRITE: dry-run by default (returns a preview); live execution requires approved:true, a non-empty auditReason, and an idempotencyKey.

SERVERAdrata SOURCE@adrata/adrata-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-adrata-mcp/approve-partner-attribution.md

What approve_partner_attribution does on Adrata

AI agents use approve_partner_attribution to create or update resources in Adrata, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Adrata environment.

Why approve_partner_attribution is rated Medium

An AI agent can call approve_partner_attribution faster than any human can review: one bad instruction and it creates or modifies resources in Adrata by the hundred, each call as confident as the last.

Questions about approve_partner_attribution

What does the approve_partner_attribution tool do? +

Approve a partner attribution (finance/ops sign-off). Writes an immutable audit row so strategic revenue stays defensible. 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 Write tool in the Adrata MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on approve_partner_attribution? +

Register the Adrata MCP server in PolicyLayer and add a rule for approve_partner_attribution: 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.

What risk level is approve_partner_attribution? +

approve_partner_attribution is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit approve_partner_attribution? +

Yes. Add a rate_limit block to the approve_partner_attribution 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.

How do I block approve_partner_attribution completely? +

Set action: deny in the PolicyLayer policy for approve_partner_attribution. 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.

What MCP server provides approve_partner_attribution? +

approve_partner_attribution 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Adrata's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.