Compute magnetic field at the center of a solenoid using B = μ₀ · n · I
AI agents call solenoid_field to retrieve information from Magnetics SME MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or calculates derived values from physics equations without side effects. It does not create, modify, delete, or execute external operations. The output is a computed result (magnetic field strength) based on standard electromagnetics formulas. This is a pure read/compute operation typical of scientific calculation tools.
From the tool's definition Tool performs a computation of magnetic field using the formula B = μ₀ · n · I, which is a mathematical calculation based on input parameters (permeability, turn density, current).
Attacks that exploit this kind of access
Compute magnetic field at the center of a solenoid using B = μ₀ · n · I. It is categorised as a Read tool in the Magnetics SME MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Magnetics SME MCP Server MCP server in PolicyLayer and add a rule for solenoid_field: 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 Magnetics SME MCP Server. Nothing to install.
solenoid_field 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 solenoid_field 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 solenoid_field. 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.
solenoid_field is provided by the Magnetics SME MCP Server MCP server (jkearney126/maxwell_bot). 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 →