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

reassign_shared_payer_account

Link and manage shared-payer account mappings for PartnerOps resellers (T2), reassigning AWS accounts under a shared payer to T3 end customers. Reassigns one AWS account under a linked shared payer - a member account or the payer's own management account - to the reseller itself or to a T3 end cu...

SERVERDoit SOURCE@doitintl/doit-mcp-server
Medium RISK CLASS
Category Write
Parameters 32 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/doit/reassign-shared-payer-account.md

What reassign_shared_payer_account does on Doit

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

ParameterTypeRequiredDescription
assetId string Yes
customerId string Yes Customer to reassign the account to: `{customerId}` (the reseller itself) or a T3 end customer within its hierarchy.
customerContext string — Scope the request to a specific customer by ID. Required for DoiT employees (whose token isn't tied to a single customer); omit for direct customer users.

Parameters from the server's own tool schema.

Why reassign_shared_payer_account is rated Medium

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

Questions about reassign_shared_payer_account

What does the reassign_shared_payer_account tool do? +

Link and manage shared-payer account mappings for PartnerOps resellers (T2), reassigning AWS accounts under a shared payer to T3 end customers. Reassigns one AWS account under a linked shared payer - a member account or the payer's own management account - to the reseller itself or to a T3 end customer within its hierarchy. Requires the SharedPayersAdmin permission and DoiT API access (platform:externalApi). User API tokens must include the permission in their scope. It is categorised as a Write tool in the Doit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does reassign_shared_payer_account accept? +

reassign_shared_payer_account accepts 3 parameters: assetId, customerId, customerContext. Required: assetId, customerId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on reassign_shared_payer_account? +

Register the Doit MCP server in PolicyLayer and add a rule for reassign_shared_payer_account: 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 Doit. Nothing to install.

What risk level is reassign_shared_payer_account? +

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

Can I rate-limit reassign_shared_payer_account? +

Yes. Add a rate_limit block to the reassign_shared_payer_account 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 reassign_shared_payer_account completely? +

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

reassign_shared_payer_account is provided by the Doit MCP server (@doitintl/doit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Doit, 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 Doit'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.