AI agents call flaw_acknowledgments_list 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 retrieves acknowledgment information associated with a flaw/CVE without creating, modifying, deleting, or executing operations. It is a simple data retrieval operation consistent with the server's read-only design. Severity is low because disclosure of acknowledgment metadata carries minimal risk.
From the tool's definition Tool name 'flaw_acknowledgments_list' and description 'Paginated acknowledgments for a flaw id' indicate retrieval of acknowledgment data. The verb 'list' and context of a read-only OSIDB querying server confirm no modifications occur.
Attacks that exploit this kind of access
Paginated acknowledgments for a flaw id (CVE or uuid). 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 flaw_acknowledgments_list: 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.
flaw_acknowledgments_list 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 flaw_acknowledgments_list 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 flaw_acknowledgments_list. 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.
flaw_acknowledgments_list 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 →