AI agents call meta_extract to retrieve information from Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | URL to analyze |
format | string | — | Output detail level (default: full) |
Parameters from the server's own tool schema.
This tool performs read-only operations by fetching and parsing publicly available SEO metadata from web pages. It has no side effects, cannot modify data, execute code, delete resources, or affect financial systems. The only information returned is metadata already published on the target URL, making it a simple retrieval operation with minimal security risk.
From the tool's definition Tool extracts and retrieves meta tags from URLs (title, description, OG tags, Twitter cards, structured data, SEO health score). The verbs 'extract' and 'returns' indicate data retrieval with no modification, deletion, or execution capabilities.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
Extract SEO meta tags from any URL. Returns title, description, OG tags, Twitter cards, structured data, and SEO health score. It is categorised as a Read tool in the Tools MCP Server, which means it retrieves data without modifying state.
meta_extract accepts 2 parameters: url, format. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Tools MCP server in PolicyLayer and add a rule for meta_extract: 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 Tools. Nothing to install.
meta_extract 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 meta_extract 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 meta_extract. 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.
meta_extract is provided by the Tools MCP server (https://www.jiebang.site/mcp). 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 →