Manage research topic preferences.
AI agents use manage_topics to create or update resources in Paper Distill MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Paper Distill MCP environment.
This tool modifies user preferences reversibly—topic preferences can be updated, added, or removed without permanent data loss or external side effects. It does not delete data irreversibly (would be Destructive), execute code (Execute), or move funds (Financial). The Write category is most appropriate as it creates or modifies data in a reversible manner.
From the tool's definition Tool name 'manage_topics' combined with description 'Manage research topic preferences' indicates creation or modification of user preferences/configuration data. The verb 'manage' in this context implies both read and write operations on topic settings.
Attacks that exploit this kind of access
Manage research topic preferences. It is categorised as a Write tool in the Paper Distill MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Paper Distill MCP server in PolicyLayer and add a rule for manage_topics: 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 Paper Distill MCP. Nothing to install.
manage_topics 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 manage_topics 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 manage_topics. 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.
manage_topics is provided by the Paper Distill MCP server (pypi:paper-distill-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 →