Next.js page/layout dosyasının SEO metadata eksiksizliğini kontrol eder. Title, description, OpenGraph, Twitter card, canonical URL, robots direktifi, structured data (JSON-LD) ve viewport tanımlarını denetler.
AI agents call check_metadata to retrieve information from MCP Frontend Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static analysis and inspection of metadata configurations. It reads and validates metadata fields but does not create, modify, delete, or execute operations. The action is purely informational—examining what metadata exists and its completeness.
From the tool's definition The tool 'check_metadata' inspects SEO metadata completeness in Next.js files by checking title, description, OpenGraph, Twitter card, canonical URL, robots directive, structured data, and viewport definitions.
Attacks that exploit this kind of access
Next.js page/layout dosyasının SEO metadata eksiksizliğini kontrol eder. Title, description, OpenGraph, Twitter card, canonical URL, robots direktifi, structured data (JSON-LD) ve viewport tanımlarını denetler. It is categorised as a Read tool in the MCP Frontend Analyzer MCP Server, which means it retrieves data without modifying state.
Register the MCP Frontend Analyzer MCP server in PolicyLayer and add a rule for check_metadata: 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 MCP Frontend Analyzer. Nothing to install.
check_metadata 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 check_metadata 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 check_metadata. 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.
check_metadata is provided by the MCP Frontend Analyzer MCP server (samet-berkay-taskin/mcp-frontend-analyzer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →