Get detailed information about all models in the current Abaqus session.
AI agents call get_model_info to retrieve information from Codex MCP Abaqus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation to fetch information about existing models. It has no capability to modify, delete, execute code, or trigger external side effects. The verb 'Get' and the passive data retrieval nature place it squarely in the Read category with low severity, as misuse would only expose design information without operational impact.
From the tool's definition Tool name 'get_model_info' and description 'Get detailed information about all models in the current Abaqus session' indicate a query operation that retrieves and returns model metadata without modifying state.
Attacks that exploit this kind of access
Get detailed information about all models in the current Abaqus session. It is categorised as a Read tool in the Codex MCP Abaqus MCP Server, which means it retrieves data without modifying state.
Register the Codex MCP Abaqus 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 Codex MCP Abaqus. 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 Codex MCP Abaqus MCP server (zhangyoupeng1996/codex_mcp_abaqus). 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 →