get_flaw_details

get_flaw_details

Server Osidb vdanen/osidb-mcp
Category Read
Risk class Low
Parameters 00 required

What get_flaw_details does on Osidb

AI agents call get_flaw_details 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.

Why get_flaw_details needs a policy

This tool retrieves vulnerability/flaw information from a read-only system. The server explicitly advertises read-only access, and the tool name and context indicate it queries existing vulnerability data without modification, deletion, or external execution. No capacity to alter state or trigger external operations.

From the tool's definition Server explicitly described as 'read-only querying' and 'MCP server for OSIDB (Red Hat Product Security's vulnerability management system).

Questions about get_flaw_details

What does the get_flaw_details tool do? +

get_flaw_details. It is categorised as a Read tool in the Osidb MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_flaw_details? +

Register the Osidb MCP server in PolicyLayer and add a rule for get_flaw_details: 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.

What risk level is get_flaw_details? +

get_flaw_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_flaw_details? +

Yes. Add a rate_limit block to the get_flaw_details 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.

How do I block get_flaw_details completely? +

Set action: deny in the PolicyLayer policy for get_flaw_details. 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.

What MCP server provides get_flaw_details? +

get_flaw_details 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.