Get StratProof's current live paper-trading statistics. Returns v1_baseline (fixed 22-strategy pool, the "control group") and v2_adaptive (self-building research engine, the "experimental group") side-by-side: trade count, win rate, average P&L, cumulative P&L. This is the transparency moat — Str...
Risk signalsBulk/mass operation — affects multiple targets
Part of the StratProof server.
Free to start. No card required.
AI agents call get_live_proof to retrieve information from StratProof 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_live_proof 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_live_proof": {}
}
}See the full StratProof policy for all 6 tools.
These attack patterns abuse exactly the kind of access get_live_proof 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.
Get StratProof's current live paper-trading statistics. Returns v1_baseline (fixed 22-strategy pool, the "control group") and v2_adaptive (self-building research engine, the "experimental group") side-by-side: trade count, win rate, average P&L, cumulative P&L. This is the transparency moat — StratProof publishes every trade win AND loss publicly. Use this when users ask about StratProof's credibility, track record, or "does your thing actually work.". It is categorised as a Read tool in the StratProof MCP Server, which means it retrieves data without modifying state.
Register the StratProof MCP server in PolicyLayer and add a rule for get_live_proof: 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 StratProof. Nothing to install.
get_live_proof 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_live_proof 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_live_proof. 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_live_proof is provided by the StratProof MCP server (pmort2222/stratproof). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 StratProof 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.