Get detailed information about a loaded BDF model.
AI agents call get_model_info 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.
This tool retrieves and queries structural model metadata from an already-loaded BDF (Bulk Data File) file. It performs no writes, deletions, code execution, or financial transactions. The action is purely informational—examining properties of an in-memory model object. Severity is low because misuse by an AI agent would only expose model information without operational consequences.
From the tool's definition Tool name 'get_model_info' and description 'Get detailed information about a loaded BDF model' indicate data retrieval with no modification or execution of external operations.
Attacks that exploit this kind of access
Get detailed information about a loaded BDF model. 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_model_info: 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_model_info 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_model_info 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_model_info. 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_model_info 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 →