Query community/people 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: - members: status, email, name, company, location - companies: name, status, location - members...
AI agents call community 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 purely retrieves or queries data about community members, companies, memberships, and check-ins without modification. The actions (list and get) are inherently read-only queries.
From the tool's definition Tool description states it is 'read-only' and supports only 'list' (retrieves entities with filters/pagination) and 'get' (retrieves single entity by ID) actions. No create, update, delete, or destructive operations are mentioned.
Attacks that exploit this kind of access
Query community/people 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: - members: status, email, name, company, location - companies: name, status, location - memberships: member, company, status - checkins: member, location, startAfter, startBefore (ISO dates — use these to get today. 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 community: 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.
community 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 community 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 community. 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.
community 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 →