Get metadata (title, description, favicon, feed list) for a host domain.
AI agents call get_host_metadata to retrieve information from Feedbagel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation retrieving publicly available metadata about a host. It does not create, modify, delete, or execute any operations—it simply fetches and returns information. The blast radius of misuse is minimal as the data retrieved is typically public metadata.
From the tool's definition Tool name 'get_host_metadata' and description stating it retrieves metadata (title, description, favicon, feed list) for a host domain. No side effects or modifications described.
Attacks that exploit this kind of access
Get metadata (title, description, favicon, feed list) for a host domain. It is categorised as a Read tool in the Feedbagel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Feedbagel MCP Server MCP server in PolicyLayer and add a rule for get_host_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 Feedbagel MCP Server. Nothing to install.
get_host_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_host_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_host_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_host_metadata is provided by the Feedbagel MCP Server MCP server (prototypr/feedbagel-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 →