Returns the full detail (title, group path, applicability, statement) for a single ISM control. Accepts either the OSCAL id (e.g. ism-principle-gov-01) or the human label (e.g. GOV-01).
AI agents call get_control 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 returns information about Australian Cyber Security Centre ISM controls. It performs a data lookup operation based on provided identifiers (OSCAL id or human label) and returns control details. There is no indication of data modification, deletion, code execution, or financial impact.
From the tool's definition Tool 'Returns the full detail' of ISM controls; accepts identifiers and retrieves data with 'no side effects'. The description explicitly indicates querying/retrieving control information without modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Returns the full detail (title, group path, applicability, statement) for a single ISM control. Accepts either the OSCAL id (e.g. ism-principle-gov-01) or the human label (e.g. GOV-01). 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 get_control: 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.
get_control 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 get_control 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 get_control. 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.
get_control 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 →