vs_monitors_get

Fetch a single monitor by id, including its current status, last check, and configuration.

Server Visual Sentinel MCP Server visualsentinel/mcp-server
Category Read
Risk class Low
Parameters 00 required

What vs_monitors_get does on Visual Sentinel MCP Server

AI agents call vs_monitors_get to retrieve information from Visual Sentinel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why vs_monitors_get needs a policy

This tool retrieves monitoring configuration and status information for a single monitor. It performs a query operation that returns data without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal—an attacker gaining access could only view monitor configurations and status, not alter monitoring rules, delete monitors, or trigger external actions.

From the tool's definition Tool name 'vs_monitors_get' and description 'Fetch a single monitor by id, including its current status, last check, and configuration' indicate data retrieval with no modification or side effects.

Questions about vs_monitors_get

What does the vs_monitors_get tool do? +

Fetch a single monitor by id, including its current status, last check, and configuration. It is categorised as a Read tool in the Visual Sentinel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on vs_monitors_get? +

Register the Visual Sentinel MCP Server MCP server in PolicyLayer and add a rule for vs_monitors_get: 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 Visual Sentinel MCP Server. Nothing to install.

What risk level is vs_monitors_get? +

vs_monitors_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit vs_monitors_get? +

Yes. Add a rate_limit block to the vs_monitors_get 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.

How do I block vs_monitors_get completely? +

Set action: deny in the PolicyLayer policy for vs_monitors_get. 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.

What MCP server provides vs_monitors_get? +

vs_monitors_get is provided by the Visual Sentinel MCP Server MCP server (visualsentinel/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.