get_unread_conversations

get_unread_conversations

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

What get_unread_conversations does on Multilead Open API MCP Server

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

This tool retrieves unread conversations from the Multilead platform. No description is provided, which slightly lowers confidence, but the naming convention strongly suggests a query operation that returns data without modification, creation, or deletion. Within the lead management and email campaign context of the platform, this is a standard Read operation to retrieve conversation state.

From the tool's definition Tool name 'get_unread_conversations' indicates retrieval of existing conversation data with no modification. The 'get' prefix and 'unread_conversations' noun phrase are characteristic of Read operations that query state without side effects.

Questions about get_unread_conversations

What does the get_unread_conversations tool do? +

get_unread_conversations. 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_unread_conversations? +

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

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

Can I rate-limit get_unread_conversations? +

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

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

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