get_manager_of_user
AI agents call get_manager_of_user to retrieve information from MCP PostgreSQL Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves organizational hierarchy information (a user's manager) without modifying, executing code, or causing side effects. It is a straightforward data retrieval operation consistent with the server's stated purpose of team hierarchy navigation. Low severity because manager information is typically non-sensitive or already accessible within an organization's directory.
From the tool's definition Tool name 'get_manager_of_user' indicates a retrieval operation. The server description emphasizes 'user name resolution and team management' with 'team hierarchy navigation', and sibling tools like 'get_team_members' and 'get_user_by_uuid' are clearly read…
Attacks that exploit this kind of access
get_manager_of_user. It is categorised as a Read tool in the MCP PostgreSQL Server MCP Server, which means it retrieves data without modifying state.
Register the MCP PostgreSQL Server MCP server in PolicyLayer and add a rule for get_manager_of_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 MCP PostgreSQL Server. Nothing to install.
get_manager_of_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_manager_of_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_manager_of_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_manager_of_user is provided by the MCP PostgreSQL Server MCP server (shubham-mishra-remotedesk/mcp-personal-efforti). 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 →