record_partner_consumption
Record committed vs consumed revenue for a partner over a period. Signature != revenue: in a consumption business revenue is realized as usage grows, and partners drive it. driver: services_delivery, marketplace, self_serve, center_of_excellence. MONEY WRITE: dry-run by default (returns a preview...
This record as markdown: /tools/adrata-adrata-mcp/record-partner-consumption.md
What record_partner_consumption does on Adrata
AI agents invoke record_partner_consumption 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 record_partner_consumption is rated High
record_partner_consumption 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 record_partner_consumption 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 record_partner_consumption, this is the rule to start with:
record_partner_consumption 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 record_partner_consumption call is checked against it from then on.
Questions about record_partner_consumption
Record committed vs consumed revenue for a partner over a period. Signature != revenue: in a consumption business revenue is realized as usage grows, and partners drive it. driver: services_delivery, marketplace, self_serve, center_of_excellence. 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 record_partner_consumption: 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.
record_partner_consumption 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 record_partner_consumption 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 record_partner_consumption. 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.
record_partner_consumption 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