AI agents call list_devices to retrieve information from Secureframe MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_' prefix combined with the server's stated read-only compliance data access model, plus consistent naming with other confirmed Read operations on this server, indicates this tool retrieves or queries device data without side effects. No modification, deletion, code execution, or financial transactions are implied.
From the tool's definition Tool name 'list_devices' follows the naming pattern of all sibling tools (list_controls, list_frameworks, list_tests, etc.), which are all read-only data retrieval operations. Server description explicitly states 'read-only access' to compliance data.
Documented attack patterns abuse exactly the kind of access list_devices gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Secureframe MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_devices:
{
"version": "1",
"default": "deny",
"tools": {
"list_devices": {}
}
}list_devices 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_devices. It is categorised as a Read tool in the Secureframe MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Secureframe MCP Server MCP server in PolicyLayer and add a rule for list_devices: 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 Secureframe MCP Server. Nothing to install.
list_devices 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_devices 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_devices. 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_devices is provided by the Secureframe MCP Server MCP server (secureframe/secureframe-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Secureframe MCP Server, 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.
11 Secureframe MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.