Get the status of an active conversation
AI agents call get_conversation_status to retrieve information from Pearl without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about an existing conversation. It has no side effects, does not execute code or commands, does not modify data, and does not delete or move resources. It is a simple query operation that falls squarely into the Read category.
From the tool's definition Tool name 'get_conversation_status' and description 'Get the status of an active conversation' indicate a read-only operation that queries and retrieves the current state of a conversation without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access get_conversation_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pearl, and nothing reaches the server without passing your rules. This is the rule we recommend for get_conversation_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_conversation_status": {}
}
}get_conversation_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the status of an active conversation. It is categorised as a Read tool in the Pearl MCP Server, which means it retrieves data without modifying state.
Register the Pearl MCP server in PolicyLayer and add a rule for get_conversation_status: 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 Pearl. Nothing to install.
get_conversation_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_conversation_status 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.
Set action: deny in the PolicyLayer policy for get_conversation_status. 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.
get_conversation_status is provided by the Pearl MCP server (pearl-com/pearl_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pearl, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Pearl tools catalogued and risk-classified — across an index of 43,000+ MCP servers.