calc_black_scholes_zomma
AI agents call calc_black_scholes_zomma to retrieve information from Black-Scholes MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
All sibling tools are calculation/read-only operations returning mathematical values derived from the Black-Scholes model. Zomma is a well-known options Greek. No side effects, no data modification, no financial transactions — purely a mathematical calculation returning a numeric result.
From the tool's definition Tool name 'calc_black_scholes_zomma' follows the pattern of sibling tools (calc_black_scholes_delta, calc_black_scholes_gamma, etc.) which calculate Black-Scholes Greeks. Zomma is a third-order Greek (rate of change of gamma with respect to volatility).
Attacks that exploit this kind of access
calc_black_scholes_zomma. It is categorised as a Read tool in the Black-Scholes MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Black-Scholes MCP Server MCP server in PolicyLayer and add a rule for calc_black_scholes_zomma: 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 Black-Scholes MCP Server. Nothing to install.
calc_black_scholes_zomma 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 calc_black_scholes_zomma 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 calc_black_scholes_zomma. 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.
calc_black_scholes_zomma is provided by the Black-Scholes MCP Server MCP server (walkingshamrock/black-scholes-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 →