AI agents invoke compute_indicators to trigger actions in Coin. 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 name implies executing a computation (likely calculating technical indicators such as RSI, MACD, etc. from market data). In context of a crypto market-data server, this is most likely a read/compute operation with no side effects, but since it 'executes' a computation and the description is empty, Execute is the most appropriate category.
From the tool's definition Tool name 'compute_indicators' suggests computation/execution of technical analysis indicators; description is empty and uninformative.
Attacks that exploit this kind of access
compute_indicators. It is categorised as a Execute tool in the Coin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Coin MCP server in PolicyLayer and add a rule for compute_indicators: 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 Coin. Nothing to install.
compute_indicators 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 compute_indicators 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 compute_indicators. 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.
compute_indicators is provided by the Coin MCP server (sweetcornna/coin-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 →