Medium Risk

create_particles

Initialise a particle system with temperature

Risk signalsCreates simulation state

Part of the Scicomp Molecular server.

create_particles can modify Scicomp Molecular data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE SCICOMP MOLECULAR →

Free to start. No card required.

AI agents use create_particles to create or modify resources in Scicomp Molecular. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call create_particles repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Scicomp Molecular.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_particles": {
      "limits": [
        {
          "counter": "create_particles_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Scicomp Molecular policy for all 12 tools.

Get this rule live on your own Scicomp Molecular server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SCICOMP MOLECULAR →

View all 12 tools →

These attack patterns abuse exactly the kind of access create_particles gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so create_particles only ever does what you allow.

SECURE SCICOMP MOLECULAR →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the create_particles tool do? +

Initialise a particle system with temperature. It is categorised as a Write tool in the Scicomp Molecular MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_particles? +

Register the Scicomp Molecular MCP server in PolicyLayer and add a rule for create_particles: 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 Scicomp Molecular. Nothing to install.

What risk level is create_particles? +

create_particles is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_particles? +

Yes. Add a rate_limit block to the create_particles 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.

How do I block create_particles completely? +

Set action: deny in the PolicyLayer policy for create_particles. 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.

What MCP server provides create_particles? +

create_particles is provided by the Scicomp Molecular MCP server (scicomp-molecular-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Scicomp Molecular tool call.

Deterministic rules across all 12 Scicomp Molecular tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.