platform.quality.tool
Get quality metrics for any tool — uptime percentage, p50/p95 latency, error rate, total calls in last 24h. Check reliability before calling expensive tools. Updated every 10 minutes. Free, no charge (APIbase)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/platform.quality.tool.md
What platform.quality.tool does on Apibase
AI agents call platform.quality.tool to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
tool_id | string | Yes | Tool ID to get quality metrics for (e.g. "crypto.get_price", "weather.get_current") |
Parameters from the server's own tool schema.
Why platform.quality.tool is rated Low
Retrieves monitoring metrics about tools without side effects or data modification.
From the tool's definition Get quality metrics, uptime percentage, latency, error rate, total calls.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs platform.quality.tool safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For platform.quality.tool, this is the rule to start with:
platform.quality.tool is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every platform.quality.tool call is checked against it from then on.
Questions about platform.quality.tool
Get quality metrics for any tool — uptime percentage, p50/p95 latency, error rate, total calls in last 24h. Check reliability before calling expensive tools. Updated every 10 minutes. Free, no charge (APIbase). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
platform.quality.tool accepts 1 parameter: tool_id. Required: tool_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for platform.quality.tool: 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 Apibase. Nothing to install.
platform.quality.tool 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 platform.quality.tool 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 platform.quality.tool. 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.
platform.quality.tool is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue