mhs5200_set_amplitude
AI agents use mhs5200_set_amplitude to create or update resources in MHS-5200A MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MHS-5200A MCP Server environment.
Based on naming convention consistent with sibling tools, this tool likely sets the amplitude parameter on a physical signal generator via serial connection. This is a Write operation (modifying a device setting). Empty description lowers confidence. Misuse could damage connected equipment if amplitude is set incorrectly, hence medium severity.
From the tool's definition Tool name: mhs5200_set_amplitude; description is empty. Sibling tools follow a pattern of 'set_*' (set_frequency, set_output, set_phase) which configure signal generator parameters.
Attacks that exploit this kind of access
mhs5200_set_amplitude. It is categorised as a Write tool in the MHS-5200A MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MHS-5200A MCP Server MCP server in PolicyLayer and add a rule for mhs5200_set_amplitude: 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_set_amplitude is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mhs5200_set_amplitude 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_set_amplitude. 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_set_amplitude 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 →