List users created after a given date (incremental sync)
AI agents call list_users_created_after to retrieve information from Mcp Cvpartner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
offset | number | — | Pagination offset |
created_after | string | Yes | Date in DD-MM-YYYY format, e.g. 27-09-2021 |
Parameters from the server's own tool schema.
This tool retrieves user records based on a date filter. It performs a read-only query operation without creating, modifying, deleting, or executing any external processes. The blast radius of misuse is minimal—an agent could retrieve user data it shouldn't access, but cannot alter or delete records. Classified as Read with low severity.
From the tool's definition Tool name contains 'list' and description states 'List users created after a given date' — a pure retrieval operation with no modification, deletion, or side effects. The mention of 'incremental sync' indicates it is designed for data synchronization queries.
Attacks that exploit this kind of access
List users created after a given date (incremental sync). It is categorised as a Read tool in the Mcp Cvpartner MCP Server, which means it retrieves data without modifying state.
list_users_created_after accepts 2 parameters: offset, created_after. Required: created_after. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Cvpartner MCP server in PolicyLayer and add a rule for list_users_created_after: 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 Cvpartner. Nothing to install.
list_users_created_after 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 list_users_created_after 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 list_users_created_after. 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.
list_users_created_after is provided by the Mcp Cvpartner MCP server (@snokam/mcp-cvpartner). 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 →