Get detailed information about a user by their ID, OID, or email.
AI agents call quire.getUser to retrieve information from Quire MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a simple data retrieval operation that queries user information without creating, modifying, or deleting data. It has no external side effects and does not execute code or perform destructive actions. The blast radius if misused is minimal—an AI agent could retrieve information about users but cannot alter data or perform privileged operations beyond read access.
From the tool's definition Tool name 'getUser' and description 'Get detailed information about a user by their ID, OID, or email' indicate retrieval of user data with no modification or side effects.
Attacks that exploit this kind of access
Get detailed information about a user by their ID, OID, or email. It is categorised as a Read tool in the Quire MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Quire MCP Server MCP server in PolicyLayer and add a rule for quire.getUser: 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 Quire MCP Server. Nothing to install.
quire.getUser 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 quire.getUser 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 quire.getUser. 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.
quire.getUser is provided by the Quire MCP Server MCP server (jacob-hartmann/quire-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 →