AI agents call get_volatility to retrieve information from OathScore without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns market volatility metrics. It performs no modifications, deletions, financial transactions, or external operations. While volatility data is used in trading decisions, the tool itself only retrieves public market information. The risk is informational only—misuse would inform poor trading decisions rather than directly cause harm.
From the tool's definition Tool retrieves 'current volatility readings' (VIX, VIX9D, VIX3M, VVIX, SKEW) and term structure data. The verb 'Get' and the nature of volatility indices as published market data indicate read-only data retrieval with no side effects.
Attacks that exploit this kind of access
Get current volatility readings: VIX, VIX9D, VIX3M, VVIX, SKEW, and term structure (contango/backwardation/flat). It is categorised as a Read tool in the OathScore MCP Server, which means it retrieves data without modifying state.
Register the OathScore MCP server in PolicyLayer and add a rule for get_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 OathScore. Nothing to install.
get_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_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_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_volatility is provided by the OathScore MCP server (moxiespirit/oathscore). 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 →