Save research findings to the session.
AI agents use save_research to create or update resources in Pathfinder MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pathfinder MCP Server environment.
This tool creates or modifies data (research findings in session storage) in a reversible manner. It does not execute code, delete data, or trigger external operations. The blast radius is minimal—worst case, incorrect research notes are saved but can be overwritten or cleared. Within the gated workflow context, this is a standard Write operation with low severity.
From the tool's definition 'Save research findings to the session' indicates persistent storage of data via write operation. The tool modifies session state by storing research outputs.
Attacks that exploit this kind of access
Save research findings to the session. It is categorised as a Write tool in the Pathfinder MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pathfinder MCP Server MCP server in PolicyLayer and add a rule for save_research: 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 Pathfinder MCP Server. Nothing to install.
save_research is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save_research 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 save_research. 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.
save_research is provided by the Pathfinder MCP Server MCP server (jamesctucker/pathfinder-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 →