Persist a research note for a prep session. Markdown content is fine.
AI agents use save_research_note_tool to create or update resources in Interview Prep — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Interview Prep environment.
This tool creates or stores a research note, which is a write operation. The data persisted is educational/preparatory notes with no side effects on external systems, financial impact, or irreversible consequences. Severity is low because misuse would only affect the user's own interview prep notes, with limited blast radius.
From the tool's definition Tool name explicitly states 'save' and description uses 'Persist a research note' — both indicate creating/storing data. Markdown content storage is reversible modification.
Attacks that exploit this kind of access
Persist a research note for a prep session. Markdown content is fine. It is categorised as a Write tool in the Interview Prep MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Interview Prep MCP server in PolicyLayer and add a rule for save_research_note_tool: 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 Interview Prep. Nothing to install.
save_research_note_tool 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_note_tool 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_note_tool. 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_note_tool is provided by the Interview Prep MCP server (shenmali/interview-mcp-first). 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 →