# 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. Agent View of the PolicyLayer registry record for `record_partner_consumption`. HTML page: https://policylayer.com/tools/adrata-adrata-mcp/record-partner-consumption ## Facts - Tool: `record_partner_consumption` - Server: Adrata (`@adrata/adrata-mcp`) — https://policylayer.com/tools/adrata-adrata-mcp.md - Install: `npx -y @adrata/adrata-mcp` - Homepage: https://www.npmjs.com/package/@adrata/adrata-mcp - Risk category: Execute (High risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Rate-limited ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "record_partner_consumption", "arguments": {} } } ``` ## 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. ## Use case 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. ## Recommended policy (PolicyLayer) Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Adrata: ```json { "version": "1", "default": "deny", "tools": { "record_partner_consumption": { "limits": [ { "counter": "record_partner_consumption_rate", "window": "minute", "max": 10, "scope": "grant" } ] } } } ``` ## Other tools on Adrata (277) - `bulk_delete_buyer_groups` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/bulk-delete-buyer-groups.md - `cancel_agent_task` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/cancel-agent-task.md - `delete_action` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-action.md - `delete_buyer_group` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-buyer-group.md - `delete_company` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-company.md - `delete_note` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-note.md - `delete_opportunity` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-opportunity.md - `delete_partner` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-partner.md - `delete_person` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-person.md - `delete_webhook` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/delete-webhook.md - `flag_work_item` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/flag-work-item.md - `forget` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/forget.md - `paper_delete_document` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/paper-delete-document.md - `paper_revoke_share` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/paper-revoke-share.md - `remove_buyer_group_member` — Destructive — https://policylayer.com/tools/adrata-adrata-mcp/remove-buyer-group-member.md - `adrata_ai_tool_execute` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/adrata-ai-tool-execute.md - `adrata_api_request` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/adrata-api-request.md - `attribute_partner_to_deal` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/attribute-partner-to-deal.md - `build_pursuit_command_center` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/build-pursuit-command-center.md - `draft_workflow` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/draft-workflow.md - `dry_run_workflow` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/dry-run-workflow.md - `replay_workflow_run` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/replay-workflow-run.md - `request_deployment` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/request-deployment.md - `request_provider_action_execution` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/request-provider-action-execution.md - `request_workflow_deployment` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/request-workflow-deployment.md - `warmup_email` — Execute — https://policylayer.com/tools/adrata-adrata-mcp/warmup-email.md - `adrata_ai_tool_catalog` — Read — https://policylayer.com/tools/adrata-adrata-mcp/adrata-ai-tool-catalog.md - `adrata_api_catalog` — Read — https://policylayer.com/tools/adrata-adrata-mcp/adrata-api-catalog.md - `adrata_desktop_app_audit` — Read — https://policylayer.com/tools/adrata-adrata-mcp/adrata-desktop-app-audit.md - `ask_matrix` — Read — https://policylayer.com/tools/adrata-adrata-mcp/ask-matrix.md - …and 247 more: https://policylayer.com/tools/adrata-adrata-mcp.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=adrata-adrata-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/adrata-adrata-mcp