Gets audit trail of all actions performed in RSpace. Optionally can filter by:
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.
This tool queries audit logs and allows filtering but does not modify, delete, or execute any operations. It is a read-only retrieval of historical audit data. Severity is low because audit logs typically contain historical information, though they may reveal sensitive activity details; however, the tool itself performs no destructive or risky operations.
From the tool's definition Tool name 'getAuditEvents' and description 'Gets audit trail of all actions performed in RSpace. Optionally can filter by' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Gets audit trail of all actions performed in RSpace. Optionally can filter by:. It is categorised as a Read tool in the RSpace MCP Server MCP Server, which means it retrieves data without modifying state.
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.
getAuditEvents 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 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.
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.
getAuditEvents is provided by the RSpace MCP Server MCP server (richarda23/rspace-mcp). 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 →