mhs5200_get_status
AI agents call mhs5200_get_status to retrieve information from MHS-5200A MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_status' pattern is a standard Read operation—querying device state with no side effects. The tool name alone provides sufficient evidence despite the empty description. The MHS-5200A is a physical instrument controller; retrieving status causes no changes to hardware state or configuration.
From the tool's definition Tool name 'mhs5200_get_status' indicates status query/retrieval operation on MHS-5200A signal generator. Tool description is empty, but the naming pattern and server context (control of generator settings) strongly suggest this retrieves current device state…
Attacks that exploit this kind of access
mhs5200_get_status. It is categorised as a Read tool in the MHS-5200A MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MHS-5200A MCP Server MCP server in PolicyLayer and add a rule for mhs5200_get_status: 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 MHS-5200A MCP Server. Nothing to install.
mhs5200_get_status 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 mhs5200_get_status 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 mhs5200_get_status. 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.
mhs5200_get_status is provided by the MHS-5200A MCP Server MCP server (naonaome/mhs5200a-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 →