find_by_author
Find entries by author/speaker
This record as markdown: /tools/jrmatherly-mcp-context-forge/find-by-author.md
What find_by_author does on ContextForge MCP Gateway
AI agents call find_by_author to retrieve information from ContextForge MCP Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why find_by_author is rated Low
This tool performs a lookup or search operation to retrieve entries matching an author/speaker criterion. It has no side effects, does not modify data, execute code, delete data, or involve financial transactions.
From the tool's definition Tool name 'find_by_author' and description 'Find entries by author/speaker' indicate a search/query operation that retrieves data without modifying it.
Attacks that exploit this kind of access
The rule that runs find_by_author safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ContextForge MCP Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find_by_author, this is the rule to start with:
find_by_author is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ContextForge MCP Gateway, apply this rule, and every find_by_author call is checked against it from then on.
Questions about find_by_author
Find entries by author/speaker. 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_by_author: 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_by_author 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_by_author 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_by_author. 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_by_author 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.
More on ContextForge MCP Gateway, and thousands of servers like it.
This server
Across the catalogue