Get feed metadata (title, description, author, etc.)
AI agents call get_feed_metadata to retrieve information from ContextForge MCP Gateway without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves informational metadata about a feed such as title, description, and author. It performs a read-only query with no capability to modify data, execute commands, delete resources, or incur financial obligations. The operation has minimal blast radius if misused by an AI agent, as it only exposes publicly available feed metadata.
From the tool's definition Tool name 'get_feed_metadata' and description 'Get feed metadata (title, description, author, etc.)' indicate a retrieval operation that queries metadata without modification or side effects.
Attacks that exploit this kind of access
Get feed metadata (title, description, author, etc.). It is categorised as a Read tool in the ContextForge MCP Gateway MCP Server, which means it retrieves data without modifying state.
Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for get_feed_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 ContextForge MCP Gateway. Nothing to install.
get_feed_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_feed_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_feed_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_feed_metadata is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). 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 →