List association tenants from Buildium.
AI agents call list_association_tenants to retrieve information from Buildium 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 or queries existing tenant data from the Buildium property management system. The verb 'list' and lack of modification language confirm it is a read-only operation. While the data queried (tenant information) may be sensitive in a property management context, the tool itself has no capability to create, modify, delete, or execute operations.
From the tool's definition Tool name 'list_association_tenants' and description 'List association tenants from Buildium' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List association tenants from Buildium. It is categorised as a Read tool in the Buildium MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Buildium MCP Server MCP server in PolicyLayer and add a rule for list_association_tenants: 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 Buildium MCP Server. Nothing to install.
list_association_tenants 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 list_association_tenants 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 list_association_tenants. 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.
list_association_tenants is provided by the Buildium MCP Server MCP server (luthersystems/mcp-server-buildium). 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 →