Add a research line you're following (used to focus proactive surfacing).
AI agents use add_interest to create or update resources in surveyHelper — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your surveyHelper environment.
This tool creates new data (a research interest entry) that can be modified or removed later. It has no side effects beyond storing a preference on the local machine, no code execution, no financial impact, and no irreversible destruction. The blast radius of misuse is minimal — an attacker could only pollute or clutter the user's interest list, requiring manual correction.
From the tool's definition Tool description states 'Add a research line' — this creates or appends a new interest record to the user's profile, a reversible write operation.
Attacks that exploit this kind of access
Add a research line you're following (used to focus proactive surfacing). It is categorised as a Write tool in the surveyHelper MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the surveyHelper MCP server in PolicyLayer and add a rule for add_interest: 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 surveyHelper. Nothing to install.
add_interest 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 add_interest 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 add_interest. 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.
add_interest is provided by the surveyHelper MCP server (rich7420/surveyhelper). 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 →