list_all_seats_of_a_specific_user

list_all_seats_of_a_specific_user

Server Multilead Open API MCP Server vanman2024/multilead-mcp
Category Read
Risk class Low
Parameters 00 required

What list_all_seats_of_a_specific_user does on Multilead Open API MCP Server

AI agents call list_all_seats_of_a_specific_user to retrieve information from Multilead Open API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_all_seats_of_a_specific_user needs a policy

This tool retrieves or queries seat information for a user with no indication of modification, deletion, or side effects. It falls squarely into the Read category. Severity is low because listing seats poses minimal risk—it's informational data retrieval within the platform's user context.

From the tool's definition Tool name 'list_all_seats_of_a_specific_user' indicates a retrieval/query operation that lists data associated with a user without modifying it. The 'list' verb and context within a lead management platform suggest read-only access to seat information.

Questions about list_all_seats_of_a_specific_user

What does the list_all_seats_of_a_specific_user tool do? +

list_all_seats_of_a_specific_user. It is categorised as a Read tool in the Multilead Open API MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_all_seats_of_a_specific_user? +

Register the Multilead Open API MCP Server MCP server in PolicyLayer and add a rule for list_all_seats_of_a_specific_user: 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 Multilead Open API MCP Server. Nothing to install.

What risk level is list_all_seats_of_a_specific_user? +

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

Can I rate-limit list_all_seats_of_a_specific_user? +

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

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

list_all_seats_of_a_specific_user is provided by the Multilead Open API MCP Server MCP server (vanman2024/multilead-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.