AI agents call osidb_status to retrieve information from Osidb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries system status information, which is a read-only operation with no side effects. It retrieves diagnostic/health data about the OSIDB API itself, similar to a health check endpoint. The low severity reflects minimal blast radius—an AI agent misusing this tool would only retrieve status metadata, causing no data modification, financial impact, or external execution.
From the tool's definition Tool description states it returns 'OSIDB API health / status payload' and the server is described as 'read-only querying'. The tool retrieves API status information without modifying or executing operations.
Attacks that exploit this kind of access
OSIDB API health / status payload. It is categorised as a Read tool in the Osidb MCP Server, which means it retrieves data without modifying state.
Register the Osidb MCP server in PolicyLayer and add a rule for osidb_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 Osidb. Nothing to install.
osidb_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 osidb_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 osidb_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.
osidb_status is provided by the Osidb MCP server (vdanen/osidb-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 →