Low Risk

view

"Top 25 most dangerous software weaknesses" / "OWASP Top 10 CWE mapping" / "CWE view [N]" — fetch a curated CWE view (a published, opinionated selection of weaknesses). View 1003 = simplified mapping (NVD uses this), view 1387 = Top 25, view 1344 = OWASP Top 10. Returns the view's metadata plus t...

Part of the Mitre Cwe server.

view is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE MITRE CWE →

Free to start. No card required.

AI agents call view to retrieve information from Mitre Cwe without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though view only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "view": {}
  }
}

See the full Mitre Cwe policy for all 27 tools.

Get this rule live on your own Mitre Cwe server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MITRE CWE →

View all 27 tools →

These attack patterns abuse exactly the kind of access view gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so view only ever does what you allow.

SECURE MITRE CWE →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the view tool do? +

"Top 25 most dangerous software weaknesses" / "OWASP Top 10 CWE mapping" / "CWE view [N]" — fetch a curated CWE view (a published, opinionated selection of weaknesses). View 1003 = simplified mapping (NVD uses this), view 1387 = Top 25, view 1344 = OWASP Top 10. Returns the view's metadata plus the included CWE IDs.. It is categorised as a Read tool in the Mitre Cwe MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on view? +

Register the Mitre Cwe MCP server in PolicyLayer and add a rule for view: 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 Mitre Cwe. Nothing to install.

What risk level is view? +

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

Can I rate-limit view? +

Yes. Add a rate_limit block to the view 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 view completely? +

Set action: deny in the PolicyLayer policy for view. 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 view? +

view is provided by the Mitre Cwe MCP server (https://gateway.pipeworx.io/mitre-cwe/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mitre Cwe tool call.

Deterministic rules across all 27 Mitre Cwe tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.