List available EMS systems. Start here to get system IDs for all other tools.
AI agents call list_ems_systems to retrieve information from EMS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward enumeration/discovery tool that returns metadata about available systems. It has no side effects, does not modify data, does not execute code or commands, and does not involve financial transactions. It is purely informational and fits the 'Read' category.
From the tool's definition Tool name 'list_ems_systems' and description 'List available EMS systems. Start here to get system IDs for all other tools' indicate a retrieval operation that queries and enumerates existing systems without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
List available EMS systems. Start here to get system IDs for all other tools. It is categorised as a Read tool in the EMS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the EMS MCP Server MCP server in PolicyLayer and add a rule for list_ems_systems: 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 EMS MCP Server. Nothing to install.
list_ems_systems 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_ems_systems 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_ems_systems. 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_ems_systems is provided by the EMS MCP Server MCP server (mattsq/ems-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 →