List attached monitors with id, name, resolution, and primary flag. Use the returned
AI agents call list_monitors to retrieve information from MTM - MCP Telegram MORE without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves system information about connected displays (monitor metadata: id, name, resolution, primary status). It performs no modifications, deletions, or external operations—purely informational reads. The blast radius of misuse is minimal; an AI agent learning about available monitors cannot cause harm. Classified as Read with low severity.
From the tool's definition Tool name 'list_monitors' and description 'List attached monitors with id, name, resolution, and primary flag' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List attached monitors with id, name, resolution, and primary flag. Use the returned. It is categorised as a Read tool in the MTM - MCP Telegram MORE MCP Server, which means it retrieves data without modifying state.
Register the MTM - MCP Telegram MORE MCP server in PolicyLayer and add a rule for list_monitors: 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 MTM - MCP Telegram MORE. Nothing to install.
list_monitors 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_monitors 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_monitors. 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_monitors is provided by the MTM - MCP Telegram MORE MCP server (v0idhrt/MTM---MCP-Telegram-MORE). 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 →