Returns a paginated, filtered list of ISM controls. Supports filters by applicability, group/section name (substring), and label prefix (e.g.
AI agents call list_controls to retrieve information from ISM 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 data from the ISM manual with no side effects. It supports filtering and pagination of existing controls but does not create, modify, delete, or execute any operations. This is a classic read operation with minimal security risk—the worst outcome would be information disclosure of publicly available security controls documentation.
From the tool's definition Tool description states 'Returns a paginated, filtered list of ISM controls' with filtering capabilities by applicability, group/section name, and label prefix. No modification, deletion, execution, or financial operations are described.
Attacks that exploit this kind of access
Returns a paginated, filtered list of ISM controls. Supports filters by applicability, group/section name (substring), and label prefix (e.g. It is categorised as a Read tool in the ISM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ISM MCP Server MCP server in PolicyLayer and add a rule for list_controls: 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 ISM MCP Server. Nothing to install.
list_controls 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_controls 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_controls. 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_controls is provided by the ISM MCP Server MCP server (rusticeagle/ism-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 →