List a tenant
AI agents call list_tenant_servers to retrieve information from Pointsyeah without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves/queries information about tenant servers. No data is created, modified, deleted, or executed. The operation is read-only with minimal blast radius if misused.
From the tool's definition Tool name 'list_tenant_servers' and description 'List a tenant' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List a tenant. It is categorised as a Read tool in the Pointsyeah MCP Server, which means it retrieves data without modifying state.
Register the Pointsyeah MCP server in PolicyLayer and add a rule for list_tenant_servers: 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 Pointsyeah. Nothing to install.
list_tenant_servers 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_tenant_servers 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_tenant_servers. 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_tenant_servers is provided by the Pointsyeah MCP server (slack-workspace-mcp-server). 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 →