osv-get-vulnerability

Fetch a single vulnerability record from OSV.dev by id. Accepts

SERVERMeta Data Mcp SOURCEpypi:meta-data-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about osv-get-vulnerability

What does the osv-get-vulnerability tool do? +

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.

How do I enforce a policy on osv-get-vulnerability? +

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.

What risk level is osv-get-vulnerability? +

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

Can I rate-limit osv-get-vulnerability? +

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.

How do I block osv-get-vulnerability completely? +

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.

What MCP server provides osv-get-vulnerability? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Meta Data's. Pull the full record:

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.