List all available Rootly API endpoints with their descriptions.
AI agents call list_endpoints to retrieve information from Rootly without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information about available API endpoints. It has no side effects, does not modify data, does not execute operations, and does not delete or move resources. It is a straightforward informational read operation with minimal security impact.
From the tool's definition Tool name 'list_endpoints' and description 'List all available Rootly API endpoints with their descriptions' indicate retrieval of metadata about available API endpoints with no modification or execution of operations.
Documented attack patterns abuse exactly the kind of access list_endpoints gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Rootly, and nothing reaches the server without passing your rules. This is the rule we recommend for list_endpoints:
{
"version": "1",
"default": "deny",
"tools": {
"list_endpoints": {}
}
}list_endpoints is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all available Rootly API endpoints with their descriptions. It is categorised as a Read tool in the Rootly MCP Server, which means it retrieves data without modifying state.
Register the Rootly MCP server in PolicyLayer and add a rule for list_endpoints: 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 Rootly. Nothing to install.
list_endpoints 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_endpoints 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_endpoints. 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_endpoints is provided by the Rootly MCP server (https://mcp.rootly.com/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Rootly, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Rootly tools catalogued and risk-classified — across an index of 43,000+ MCP servers.