getAuditEvents

getAuditEvents

Server RSpace MCP Server rspace-os/rspace-mcp
Category Read
Risk class Low
Parameters 00 required

What getAuditEvents does on RSpace MCP Server

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

Why getAuditEvents needs a policy

Audit events are read-only historical records. While retrieving audit logs is a Read operation (no side effects), the severity is medium rather than low because audit logs may contain sensitive information about system activities, user actions, and potentially confidential research data access patterns.

From the tool's definition Tool name 'getAuditEvents' indicates retrieval of audit event logs. Based on naming convention and the context of an RSpace research data management system, this tool queries historical audit data rather than modifying it.

Questions about getAuditEvents

What does the getAuditEvents tool do? +

getAuditEvents. It is categorised as a Read tool in the RSpace MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getAuditEvents? +

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

What risk level is getAuditEvents? +

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

Can I rate-limit getAuditEvents? +

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

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

getAuditEvents is provided by the RSpace MCP Server MCP server (rspace-os/rspace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.