New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

cursor_get_daily_active_users

Get daily active user counts for a date range

SERVERSage MCP SOURCEsagemcp/sagemcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/cursor-get-daily-active-users.md

What cursor_get_daily_active_users does on Sage MCP

AI agents call cursor_get_daily_active_users to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why cursor_get_daily_active_users is rated Low

This tool performs a read-only retrieval of historical user activity metrics. It queries existing data for a specified date range and returns aggregated statistics. No data is created, modified, deleted, or financial transactions are involved. The action is informational only with no side effects. Low severity because exposure of user count metrics is typically non-sensitive compared to user PII or system access.

From the tool's definition Tool name 'cursor_get_daily_active_users' and description 'Get daily active user counts for a date range' indicate a query operation that retrieves analytics/metrics data without modification, deletion, or execution of external operations.

Questions about cursor_get_daily_active_users

What does the cursor_get_daily_active_users tool do? +

Get daily active user counts for a date range. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cursor_get_daily_active_users? +

Register the Sage MCP server in PolicyLayer and add a rule for cursor_get_daily_active_users: 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 Sage MCP. Nothing to install.

What risk level is cursor_get_daily_active_users? +

cursor_get_daily_active_users is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cursor_get_daily_active_users? +

Yes. Add a rate_limit block to the cursor_get_daily_active_users 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.

How do I block cursor_get_daily_active_users completely? +

Set action: deny in the PolicyLayer policy for cursor_get_daily_active_users. 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.

What MCP server provides cursor_get_daily_active_users? +

cursor_get_daily_active_users is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Sage, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sage's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.