Power of two numbers
AI agents invoke power to trigger actions in MCP Server & Client Test Environment. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool name and description suggest a simple mathematical exponentiation operation (Read/Other level), but the server context explicitly mentions shell command execution capabilities. Given the ambiguous description and the presence of 'run_server_command' as a sibling tool, there's some uncertainty. Most likely this is a pure math function (raising a number to a power), which would be Read/Other.
From the tool's definition Tool name: 'power', description: 'Power of two numbers'; server description mentions 'shell command execution' and sibling tool 'run_server_command'
Attacks that exploit this kind of access
Power of two numbers. It is categorised as a Execute tool in the MCP Server & Client Test Environment MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Server & Client Test Environment MCP server in PolicyLayer and add a rule for power: 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 MCP Server & Client Test Environment. Nothing to install.
power is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the power 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 power. 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.
power is provided by the MCP Server & Client Test Environment MCP server (mayur11235/lets-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 →