Check the status of a ProofStream verification request by case ID. Status values: - pending_review: Request received, awaiting ProofStream acceptance - confirmed: Accepted, payment captured, verification scheduled - scheduled: Verification date/time confirmed - in_progress: Verifier on-site, live...
AI agents call proofstream_check_status to retrieve information from ProofStream MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves status information about an existing verification request. It performs a query operation with no ability to modify data, trigger charges, execute code, or delete anything. The return of status enums demonstrates a simple information lookup. While the parent server involves payment capture in other tools (proofstream_submit_request), this specific tool is purely informational.
From the tool's definition Tool description states 'Check the status of a ProofStream verification request by case ID.' The status values listed (pending_review, confirmed, scheduled, in_progress, completed, cancelled) are all read-only states that indicate query results with no side…
Attacks that exploit this kind of access
Check the status of a ProofStream verification request by case ID. Status values: - pending_review: Request received, awaiting ProofStream acceptance - confirmed: Accepted, payment captured, verification scheduled - scheduled: Verification date/time confirmed - in_progress: Verifier on-site, livestream active (if requested) - completed: Verification done, report delivered to email - cancelled: Request declined (no charge) When status is. It is categorised as a Read tool in the ProofStream MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ProofStream MCP Server MCP server in PolicyLayer and add a rule for proofstream_check_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 ProofStream MCP Server. Nothing to install.
proofstream_check_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 proofstream_check_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 proofstream_check_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.
proofstream_check_status is provided by the ProofStream MCP Server MCP server (proofstreamai/proofstream-mcp). 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 →