Poll the status of a proof job. Returns the current state (queued, processing, complete, failed) and progress details. Prefer cuecrux_session as your first and only direct MCP call. It returns a typed capability plan that routes this tool (and every other) to its preferred channel, tier, and cost...
Risk signalsBulk/mass operation — affects multiple targets
Part of the VaultCrux Memory Core server.
Free to start. No card required.
AI agents call get_proof_status to retrieve information from VaultCrux Memory Core without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_proof_status only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_proof_status": {}
}
}See the full VaultCrux Memory Core policy for all 76 tools.
These attack patterns abuse exactly the kind of access get_proof_status gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Poll the status of a proof job. Returns the current state (queued, processing, complete, failed) and progress details. Prefer cuecrux_session as your first and only direct MCP call. It returns a typed capability plan that routes this tool (and every other) to its preferred channel, tier, and cost class. One call per session is enough; the plan is the source of routing truth for all subsequent work. This tool remains directly callable for backward compatibility; the collapsed surface is the intended surface.. It is categorised as a Read tool in the VaultCrux Memory Core MCP Server, which means it retrieves data without modifying state.
Register the VaultCrux Memory Core MCP server in PolicyLayer and add a rule for get_proof_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 VaultCrux Memory Core. Nothing to install.
get_proof_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_proof_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_proof_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_proof_status is provided by the VaultCrux Memory Core MCP server (https://api.vaultcrux.com/platform/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 76 VaultCrux Memory Core tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.