frontend_security_audit_manifest

SERVERDataNexus MCP SOURCEdev-7bd0/mcp-server

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-7bd0-mcp-server/frontend-security-audit-manifest.md

WHAT IT DOES

What frontend_security_audit_manifest does on DataNexus MCP

AI agents call frontend_security_audit_manifest to retrieve information from DataNexus MCP 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
`lockfile`	object	—	Contents of package-lock.json or yarn.lock. Optional.
`manifest`	string	—	Contents of package.json as a string. Required. 500 KB max.

Parameters from the server's own tool schema.

RISK

Why frontend_security_audit_manifest is rated Low

This is a pure analysis/query tool. It retrieves and evaluates security metadata from provided package manifests but does not create, modify, delete, or execute any code. It returns informational verdicts about risks without making any changes to systems or data. This is classic Read category behavior—introspection without side effects.

From the tool's definition Tool performs security audits of frontend package manifests and returns verdicts (SHIP/CAUTION/BLOCK) with licensing and vulnerability analysis. The description explicitly states it 'audits' and 'returns' findings.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs frontend_security_audit_manifest safely

PolicyLayer is an MCP gateway: it sits between your AI agents and DataNexus MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For frontend_security_audit_manifest, this is the rule to start with:

frontend_security_audit_manifest Allowed

frontend_security_audit_manifest is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "frontend_security_audit_manifest": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect DataNexus MCP, apply this rule, and every frontend_security_audit_manifest call is checked against it from then on.

FAQ

Questions about frontend_security_audit_manifest

What does the frontend_security_audit_manifest tool do? +

Audit a frontend package.json for security risks — returns a single SHIP/CAUTION/BLOCK verdict with licence risks and abandonment signals. Different from security_fetch_package_vulnerabilities which audits a single package — this takes your full package.json. manifest: Contents of package.json as a string. Required. 500 KB max. lockfile: Contents of package-lock.json or yarn.lock (optional). If provided, audits pinned versions; otherwise audits semver ranges. BLOCK: any critical CVE in direct deps OR GPL-3.0 in commercial context. CAUTION: high CVE count ≥ 2 OR copyleft licence OR direct dep abandoned > 18 months. Sources: OSV.dev (CVEs), deps.dev (licences), npm registry (abandonment). Read-only. No side effects. Idempotent. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="frontend_security_audit_manifest", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}". It is categorised as a Read tool in the DataNexus MCP MCP Server, which means it retrieves data without modifying state.

What parameters does frontend_security_audit_manifest accept? +

frontend_security_audit_manifest accepts 2 parameters: lockfile, manifest. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on frontend_security_audit_manifest? +

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

What risk level is frontend_security_audit_manifest? +

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

Can I rate-limit frontend_security_audit_manifest? +

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

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

frontend_security_audit_manifest is provided by the DataNexus MCP server (dev-7bd0/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on DataNexus, and thousands of servers like it.

This server

All 55 DataNexus tools →

Across the catalogue

emit_second_audit on 0sec → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →