Extract displacement results from OP2 file.
AI agents call get_displacement to retrieve information from pyNastran MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves pre-computed displacement results from an OP2 (Nastran output) file. No data is created, modified, deleted, or used to trigger external operations. The verb 'extract' indicates querying/retrieving existing analysis results. This is consistent with other sibling tools on the server (get_nodes, get_elements, get_materials) which are all read operations.
From the tool's definition Tool name 'get_displacement' and description 'Extract displacement results from OP2 file' indicate retrieval of analysis results without modification. This is a read-only operation on existing FEA output data.
Attacks that exploit this kind of access
Extract displacement results from OP2 file. It is categorised as a Read tool in the pyNastran MCP Server MCP Server, which means it retrieves data without modifying state.
Register the pyNastran MCP Server MCP server in PolicyLayer and add a rule for get_displacement: 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 pyNastran MCP Server. Nothing to install.
get_displacement 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_displacement 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_displacement. 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_displacement is provided by the pyNastran MCP Server MCP server (shaoqigit/pynastran-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 →