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

list_shared_payer_account_mappings

Link and manage shared-payer account mappings for PartnerOps resellers (T2), reassigning AWS accounts under a shared payer to T3 end customers. Lists the AWS accounts under the reseller's linked shared payers, together with the end customer each is currently mapped to. {customerId} (the reseller ...

SERVERDoit SOURCE@doitintl/doit-mcp-server
Low RISK CLASS
Category Read
Parameters 31 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

What list_shared_payer_account_mappings does on Doit

AI agents call list_shared_payer_account_mappings to retrieve information from Doit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
customerId string Yes
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.
managementAccount string —

Parameters from the server's own tool schema.

Why list_shared_payer_account_mappings is rated Low

Even though list_shared_payer_account_mappings 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.

Questions about list_shared_payer_account_mappings

What does the list_shared_payer_account_mappings tool do? +

Link and manage shared-payer account mappings for PartnerOps resellers (T2), reassigning AWS accounts under a shared payer to T3 end customers. Lists the AWS accounts under the reseller's linked shared payers, together with the end customer each is currently mapped to. {customerId} (the reseller itself) means the account has not yet been reassigned to an end customer. Each payer's own management account is included alongside its member accounts. 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 Read tool in the Doit MCP Server, which means it retrieves data without modifying state.

What parameters does list_shared_payer_account_mappings accept? +

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

How do I enforce a policy on list_shared_payer_account_mappings? +

Register the Doit MCP server in PolicyLayer and add a rule for list_shared_payer_account_mappings: 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 list_shared_payer_account_mappings? +

list_shared_payer_account_mappings is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_shared_payer_account_mappings? +

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

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

list_shared_payer_account_mappings 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.

// 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.