Get user presences within a date range with daily aggregation and total calculations
AI agents call get_user_presences to retrieve information from MoCo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves presence data (likely attendance/availability records) filtered by date range, performing aggregation and calculations on read data. It has no side effects, does not modify state, and does not trigger external operations.
From the tool's definition Tool name 'get_user_presences' and description 'Get user presences within a date range with daily aggregation and total calculations' indicate pure data retrieval with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get user presences within a date range with daily aggregation and total calculations. It is categorised as a Read tool in the MoCo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MoCo MCP Server MCP server in PolicyLayer and add a rule for get_user_presences: 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 MoCo MCP Server. Nothing to install.
get_user_presences 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_presences 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_presences. 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_presences is provided by the MoCo MCP Server MCP server (niondigital/moco-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 →