cursor_get_agent_edits

Get team agent edit analytics 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-agent-edits.md

WHAT IT DOES

What cursor_get_agent_edits does on Sage MCP

AI agents call cursor_get_agent_edits 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.

RISK

Why cursor_get_agent_edits is rated Low

This tool retrieves analytics data (agent edit history/metrics) for a specified date range. The 'get_' verb and 'analytics' terminology confirm it is a read-only query operation that observes historical data without side effects. No data is created, modified, deleted, or executed.

From the tool's definition Tool name contains 'get_' prefix and description states 'Get team agent edit analytics' - both indicate retrieval of data without modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cursor_get_agent_edits safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cursor_get_agent_edits, this is the rule to start with:

cursor_get_agent_edits Allowed

cursor_get_agent_edits is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cursor_get_agent_edits": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every cursor_get_agent_edits call is checked against it from then on.

FAQ

Questions about cursor_get_agent_edits

What does the cursor_get_agent_edits tool do? +

Get team agent edit analytics 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_agent_edits? +

Register the Sage MCP server in PolicyLayer and add a rule for cursor_get_agent_edits: 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_agent_edits? +

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

Can I rate-limit cursor_get_agent_edits? +

Yes. Add a rate_limit block to the cursor_get_agent_edits 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_agent_edits completely? +

Set action: deny in the PolicyLayer policy for cursor_get_agent_edits. 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_agent_edits? +

cursor_get_agent_edits 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.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

get_agent on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →