AI agents call affect_cvss_scores_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 CVSS score information associated with affects in OSIDB. It performs data retrieval with no side effects, modifications, or irreversible actions. The explicit 'read-only' nature of the server and naming convention consistent with other list/get operations confirm Read category. Severity is low because CVSS scores are public vulnerability metadata intended for disclosure.
From the tool's definition Tool name 'affect_cvss_scores_list' and server description states 'read-only querying' of affects and related data. Pattern matches sibling tools (affect_get, affects_list, flaw_cvss_scores_list) which are all read operations.
Attacks that exploit this kind of access
affect_cvss_scores_list. 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 affect_cvss_scores_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.
affect_cvss_scores_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 affect_cvss_scores_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 affect_cvss_scores_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.
affect_cvss_scores_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 →