get_assets
AI agents call get_assets 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.
Although the description is empty, the tool name 'get_assets' and context strongly suggest a retrieval operation with no side effects. No modification, deletion, code execution, or financial impact is indicated. Confidence is reduced slightly due to missing description, but the Read category is the most reasonable classification given the server's analytics and monitoring focus and the pattern of sibling tools.
From the tool's definition Tool name is 'get_assets' on an Event Monitoring System server. Sibling tools include 'list_databases', 'list_ems_systems', 'list_event_profiles', and 'query_database'—all Read operations.
Attacks that exploit this kind of access
get_assets. 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 get_assets: 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.
get_assets 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_assets 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_assets. 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_assets 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 →