Low Risk

copilot_list_audit_events

List Copilot-related audit log events for an organization

How to control copilot_list_audit_events ↓

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

Low Risk

This tool queries and retrieves audit log events for informational purposes. Listing audit events is a read-only operation that has no side effects on any system or data. While audit logs may contain sensitive information, the act of reading logs does not alter state or create risk of unintended consequences from parameter injection.

From the tool's definition Tool name contains 'list' and description states 'List Copilot-related audit log events' — purely retrieves audit log data with no modification, deletion, or execution capability.

Documented attack patterns abuse exactly the kind of access copilot_list_audit_events gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for copilot_list_audit_events:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "copilot_list_audit_events": {}
  }
}

copilot_list_audit_events is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Sage MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the copilot_list_audit_events tool do? +

List Copilot-related audit log events for an organization. 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 copilot_list_audit_events? +

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

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

Can I rate-limit copilot_list_audit_events? +

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

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

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

Enforce policy on every Sage MCP tool call.

Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.