cwe_lookup
MITRE CWE detail by ID (format CWE-NNN or NNN). Returns name, abstraction, status, description, and parent/child CWE relationships.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/cwe-lookup.md
What cwe_lookup does on Livedatalink
AI agents call cwe_lookup to retrieve information from Livedatalink without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
cwe_id | string | Yes | CWE identifier, e.g. CWE-79. |
Parameters from the server's own tool schema.
Why cwe_lookup is rated Low
This is a read-only query tool that retrieves information about Common Weakness Enumeration entries from the MITRE database. It has no side effects—it cannot modify data, execute code, or trigger external operations. The blast radius of misuse is minimal; an attacker gaining access could only enumerate CWE information already publicly available. Confidence is high due to clear read-only semantics.
From the tool's definition Tool performs lookup and returns CWE details (name, abstraction, status, description, relationships) with no modification or execution capability. Keywords: 'detail by ID', 'Returns' indicate pure data retrieval.
Attacks that exploit this kind of access
The rule that runs cwe_lookup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cwe_lookup, this is the rule to start with:
cwe_lookup 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 Livedatalink, apply this rule, and every cwe_lookup call is checked against it from then on.
Questions about cwe_lookup
MITRE CWE detail by ID (format CWE-NNN or NNN). Returns name, abstraction, status, description, and parent/child CWE relationships. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
cwe_lookup accepts 1 parameter: cwe_id. Required: cwe_id. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for cwe_lookup: 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 Livedatalink. Nothing to install.
cwe_lookup 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 cwe_lookup 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 cwe_lookup. 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.
cwe_lookup is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue