// MCP TOOL REFERENCE

AUTOMOTIVE CYBERSECURITY TOOLS

6 tools from the Automotive Cybersecurity MCP Server, categorised by risk level.

View the Automotive Cybersecurity policy →

READ TOOLS

about Server metadata, dataset statistics, freshness, and provenance. Call this to verify data coverage, currency, and content basis before relying on re... get_requirement Retrieve a specific regulation article or standard clause. For regulations (UNECE R155/R156), returns full text. For standards (ISO 21434), returns... list_sources List available automotive cybersecurity regulations and standards. Returns metadata including version, type (regulation/standard), item counts, and... list_work_products List ISO 21434 work products (deliverables) required for cybersecurity engineering. Shows which artifacts to produce for each clause, whether CAL-d... search_requirements Full-text search across all regulations and standards using FTS5 with BM25 ranking. Search regulations (UNECE R155/R156 full text) and standards (I... 2/5

WRITE TOOLS

export_compliance_matrix Generate a compliance traceability matrix showing regulation requirements mapped to ISO 21434 clauses and work products. Export as Markdown table o... 2/5

// FAQ

How many tools does the Automotive Cybersecurity MCP server have? +

The Automotive Cybersecurity MCP server exposes 6 tools across 2 categories: Read, Write.

How do I enforce policies on Automotive Cybersecurity tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Automotive Cybersecurity server.

What risk categories do Automotive Cybersecurity tools fall into? +

Automotive Cybersecurity tools are categorised as Read (5), Write (1). Each category has a recommended default policy.

Enforce policies on Automotive Cybersecurity

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →