results_global_evaluate
AI agents use results_global_evaluate to create or update resources in COMSOL MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your COMSOL MCP Server environment.
An AI agent can call results_global_evaluate faster than any human can review — one bad instruction and it creates or modifies resources in COMSOL MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
results_global_evaluate. It is categorised as a Write tool in the COMSOL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the COMSOL MCP Server MCP server in PolicyLayer and add a rule for results_global_evaluate: 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 COMSOL MCP Server. Nothing to install.
results_global_evaluate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the results_global_evaluate 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 results_global_evaluate. 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.
results_global_evaluate is provided by the COMSOL MCP Server MCP server (zhangyoupeng1996/codex_mcp_comsol). 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 →