Returns the Zotero user ID configured in the server environment. Needed by the standalone inject-citations skill script (inject.js) to generate Zotero field code URIs. Not needed when using the inject_citations MCP tool, which reads the userId internally.
AI agents call get_user_id to retrieve information from Mcp Zotero without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a configuration value (user ID) without modifying, creating, executing, or deleting anything. It is a straightforward read operation. Severity is low because user IDs are typically semi-public identifiers and leaking one does not directly compromise data access (authentication tokens would be more sensitive).
From the tool's definition Tool 'get_user_id' returns a user ID value; the description explicitly states it 'Returns the Zotero user ID configured in the server environment.' This is a pure retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_user_id gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Zotero, and nothing reaches the server without passing your rules. This is the rule we recommend for get_user_id:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_id": {}
}
}get_user_id is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns the Zotero user ID configured in the server environment. Needed by the standalone inject-citations skill script (inject.js) to generate Zotero field code URIs. Not needed when using the inject_citations MCP tool, which reads the userId internally. It is categorised as a Read tool in the Mcp Zotero MCP Server, which means it retrieves data without modifying state.
Register the Mcp Zotero MCP server in PolicyLayer and add a rule for get_user_id: 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 Mcp Zotero. Nothing to install.
get_user_id 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 get_user_id 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 get_user_id. 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.
get_user_id is provided by the Mcp Zotero MCP server (xevos117/mcp-zotero). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Zotero, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Mcp Zotero tools catalogued and risk-classified — across an index of 43,000+ MCP servers.