Get current and historical volatility metrics for a coin. Useful for agents deciding position sizes.
AI agents call get_market_volatility to retrieve information from Agenti without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves market data (volatility metrics). It has no side effects—it does not execute trades, transfer funds, modify balances, or delete data. While the server context involves cryptocurrency operations, this specific tool is purely Read-category: it gathers information to inform decisions but does not execute those decisions.
From the tool's definition Tool name 'get_market_volatility' and description state it retrieves 'current and historical volatility metrics' with no mention of modification, deletion, or financial transactions.
Documented attack patterns abuse exactly the kind of access get_market_volatility gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agenti, and nothing reaches the server without passing your rules. This is the rule we recommend for get_market_volatility:
{
"version": "1",
"default": "deny",
"tools": {
"get_market_volatility": {}
}
}get_market_volatility is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get current and historical volatility metrics for a coin. Useful for agents deciding position sizes. It is categorised as a Read tool in the Agenti MCP Server, which means it retrieves data without modifying state.
Register the Agenti MCP server in PolicyLayer and add a rule for get_market_volatility: 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 Agenti. Nothing to install.
get_market_volatility 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 get_market_volatility 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 get_market_volatility. 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.
get_market_volatility is provided by the Agenti MCP server (nirholas/agenti). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 73 Agenti tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
73 Agenti tools catalogued and risk-classified — across an index of 42,500+ MCP servers.