AI agents call get-user to retrieve information from Notion MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves user information, which is a read-only operation with no side effects. Even though the description is empty, the naming pattern is clear and consistent with other read operations on the server. Severity is low as user information retrieval poses minimal risk; an AI agent misusing this would have limited negative impact.
From the tool's definition Tool name is 'get-user' with no description provided. The 'get-' prefix and sibling tools like 'get-page', 'get-database', 'get-block' consistently indicate retrieval operations. 'get-user' retrieves user information without modifying data.
Documented attack patterns abuse exactly the kind of access get-user gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Notion MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-user:
{
"version": "1",
"default": "deny",
"tools": {
"get-user": {}
}
}get-user 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.
get-user. It is categorised as a Read tool in the Notion MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Notion MCP Server MCP server in PolicyLayer and add a rule for get-user: 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 Notion MCP Server. Nothing to install.
get-user 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 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. 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 is provided by the Notion MCP Server MCP server (ramidecodes/mcp-server-notion). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Notion MCP Server, 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.
17 Notion MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.