Submit a human verification request to ProofStream. A real human will go on-site with a camera, livestream the verification, and deliver a timestamped evidence report (photo + video + written findings). Use this when your workflow requires physical confirmation of something in the real world. Ser...
AI agents use proofstream_submit_request to create or update resources in ProofStream MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ProofStream MCP Server environment.
An AI agent can call proofstream_submit_request faster than any human can review — one bad instruction and it creates or modifies resources in ProofStream MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Submit a human verification request to ProofStream. A real human will go on-site with a camera, livestream the verification, and deliver a timestamped evidence report (photo + video + written findings). Use this when your workflow requires physical confirmation of something in the real world. Services available: - product_verification ($39 standard / $79 with livestream): Authenticate a physical product — serial numbers, packaging, labels, authentication markers. - document_verification ($99 standard / $149 with livestream): Confirm a physical document exists, matches claimed content, photograph stamps/signatures/seals. - property_asset_check ($249 standard / $349 with livestream): On-site visual condition documentation of a property, vehicle, or asset. Urgency options: standard (24-72 hours), rush (+50%, within 24h), same_day (+100%) Returns a case_id you can use to check status. Card is authorized but NOT charged until ProofStream accepts the request. It is categorised as a Write tool in the ProofStream MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ProofStream MCP Server MCP server in PolicyLayer and add a rule for proofstream_submit_request: 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_submit_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the proofstream_submit_request 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_submit_request. 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_submit_request 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 →