get_conversations_by_identifiers

get_conversations_by_identifiers

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

What get_conversations_by_identifiers does on Multilead Open API MCP Server

AI agents call get_conversations_by_identifiers 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 get_conversations_by_identifiers needs a policy

The 'get_' prefix and 'by_identifiers' pattern indicate a data retrieval operation that queries conversations based on provided identifiers. This is a Read operation—it fetches data with no side effects. Despite the empty description lowering confidence slightly, the verb and naming convention strongly suggest passive data retrieval rather than modification, execution, or deletion.

From the tool's definition Tool name 'get_conversations_by_identifiers' uses the 'get' verb, which retrieves data without modification. No description provided, but the retrieval pattern is consistent with Read operations in the Multilead API context.

Questions about get_conversations_by_identifiers

What does the get_conversations_by_identifiers tool do? +

get_conversations_by_identifiers. 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 get_conversations_by_identifiers? +

Register the Multilead Open API MCP Server MCP server in PolicyLayer and add a rule for get_conversations_by_identifiers: 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 get_conversations_by_identifiers? +

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

Can I rate-limit get_conversations_by_identifiers? +

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

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

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