Find related entries to a specific entry
AI agents call find_related_entries 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 performs a read-only lookup operation to discover relationships or connections between entries in what appears to be a content management or knowledge graph system. The operation has no side effects—it does not create, modify, delete, or execute arbitrary code. The verb 'find' and the passive nature of querying for related items confirm this is a retrieval operation with minimal blast radius.
From the tool's definition Tool name 'find_related_entries' and description 'Find related entries to a specific entry' indicate a search/query operation that retrieves related data without modifying state.
Attacks that exploit this kind of access
Find related entries to a specific entry. 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 find_related_entries: 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.
find_related_entries 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 find_related_entries 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 find_related_entries. 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.
find_related_entries 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 →