Query collaboration data in OfficeRnD. action=list: List entities with optional filters and pagination (max 50 per page). action=get: Get a single entity by ID. Entity-specific filters when listing: - events: location, startAfter, startBefore (ISO dates) - tickets: status, member, location - post...
AI agents call collaboration to retrieve information from OfficeRnD MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries collaboration entities (events, tickets, posts) without side effects. The available actions are purely read operations: listing entities with optional filters and pagination, and fetching individual records by ID. No create, update, delete, or execute operations are supported. The read-only nature of the server and tool design confirm this classification.
From the tool's definition Tool performs only 'list' and 'get' actions to query collaboration data with filters and pagination; no mutation or deletion capabilities described; server explicitly described as 'read-only'.
Attacks that exploit this kind of access
Query collaboration data in OfficeRnD. action=list: List entities with optional filters and pagination (max 50 per page). action=get: Get a single entity by ID. Entity-specific filters when listing: - events: location, startAfter, startBefore (ISO dates) - tickets: status, member, location - posts: (pagination only). It is categorised as a Read tool in the OfficeRnD MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OfficeRnD MCP Server MCP server in PolicyLayer and add a rule for collaboration: 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 OfficeRnD MCP Server. Nothing to install.
collaboration 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 collaboration 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 collaboration. 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.
collaboration is provided by the OfficeRnD MCP Server MCP server (mrboor/officernd-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 →