osv-get-vulnerability
Fetch a single vulnerability record from OSV.dev by id. Accepts
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/osv-get-vulnerability.md
What osv-get-vulnerability does on Meta Data Mcp
AI agents call osv-get-vulnerability to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why osv-get-vulnerability is rated Low
This tool retrieves vulnerability data from a public database. It performs a query operation with no capability to modify, delete, or execute code. The data returned is informational only. Even though the data concerns vulnerabilities, the tool itself is a read-only query against an open API, making it a Read category with low severity.
From the tool's definition Tool name is 'osv-get-vulnerability' and description states 'Fetch a single vulnerability record from OSV.dev by id'. The verb 'Fetch' and context of querying an open data API (OSV.dev) indicates retrieval without modification or side effects.
Attacks that exploit this kind of access
The rule that runs osv-get-vulnerability safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For osv-get-vulnerability, this is the rule to start with:
osv-get-vulnerability 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 Meta Data Mcp, apply this rule, and every osv-get-vulnerability call is checked against it from then on.
Questions about osv-get-vulnerability
Fetch a single vulnerability record from OSV.dev by id. Accepts. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.
Register the Meta Data MCP server in PolicyLayer and add a rule for osv-get-vulnerability: 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 Meta Data Mcp. Nothing to install.
osv-get-vulnerability 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 osv-get-vulnerability 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 osv-get-vulnerability. 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.
osv-get-vulnerability is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Data, and thousands of servers like it.
This server
Across the catalogue