Return {reviewed, decision_result} for a thread.
AI agents call check_review_status to retrieve information from Sales MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns existing review status information without creating, modifying, deleting, or executing any operations. It is a read-only query operation with minimal blast radius - an AI agent misusing this tool could only access status information it may not be authorized to see, but cannot alter sales data or trigger financial transactions.
From the tool's definition Tool name 'check_review_status' and description 'Return {reviewed, decision_result} for a thread' indicate a retrieval operation that queries the status of a review thread without modifying any data.
Attacks that exploit this kind of access
Return {reviewed, decision_result} for a thread. It is categorised as a Read tool in the Sales MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sales MCP Server MCP server in PolicyLayer and add a rule for check_review_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 Sales MCP Server. Nothing to install.
check_review_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 check_review_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 check_review_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.
check_review_status is provided by the Sales MCP Server MCP server (pessini/langgraph-mcp-prefab-ui). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →