Get real-time API inference performance for LLM models - TTFT p50/p95 (time-to-first-token latency), throughput (tokens/sec), and 24-hour success rate. Use this alongside get_api_pricing to make routing decisions: cheapest model that is currently operational and fast enough for your latency budge...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Tickerr Live Status server.
Free to start. No card required.
AI agents call get_model_performance to retrieve information from Tickerr Live Status 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_model_performance 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_model_performance": {}
}
}See the full Tickerr Live Status policy for all 9 tools.
These attack patterns abuse exactly the kind of access get_model_performance 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 real-time API inference performance for LLM models - TTFT p50/p95 (time-to-first-token latency), throughput (tokens/sec), and 24-hour success rate. Use this alongside get_api_pricing to make routing decisions: cheapest model that is currently operational and fast enough for your latency budget. Covers anthropic, openai, google, groq, mistral, cerebras, cohere, xai, openrouter. Updated every 5 minutes via live API calls.. It is categorised as a Read tool in the Tickerr Live Status MCP Server, which means it retrieves data without modifying state.
Register the Tickerr Live Status MCP server in PolicyLayer and add a rule for get_model_performance: 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 Tickerr Live Status. Nothing to install.
get_model_performance 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_model_performance 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_model_performance. 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_model_performance is provided by the Tickerr Live Status MCP server (imviky-zzzr/tickerr-live-status). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Tickerr Live Status 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.