Extract title, description, Open Graph tags, Twitter Card data, canonical URL, favicon,
AI agents call get_metadata to retrieve information from ToolCenter MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves publicly available metadata from web pages. It performs a query operation that returns information without creating, modifying, deleting, or executing any code. The blast radius of misuse is minimal—an agent could retrieve metadata from many pages, but no data is altered and no external operations are triggered. This is a straightforward Read operation.
From the tool's definition Tool description indicates it 'Extract[s]' metadata fields (title, description, Open Graph tags, Twitter Card data, canonical URL, favicon).
Attacks that exploit this kind of access
Extract title, description, Open Graph tags, Twitter Card data, canonical URL, favicon,. It is categorised as a Read tool in the ToolCenter MCP MCP Server, which means it retrieves data without modifying state.
Register the ToolCenter MCP server in PolicyLayer and add a rule for get_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 ToolCenter MCP. Nothing to install.
get_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 get_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 get_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.
get_metadata is provided by the ToolCenter MCP server (toolcenter-dev/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 →