Low Risk

describe_opt_demo

Full detail on one optimization demo — controls, available scenario keys, sites, fixed parameters, citations, and the key finding the demo illustrates. Use this before get_opt_result to know what scenario_key values are accepted.

Part of the SCModeling server.

describe_opt_demo is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE SCMODELING →

Free to start. No card required.

AI agents call describe_opt_demo to retrieve information from SCModeling without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though describe_opt_demo only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "describe_opt_demo": {}
  }
}

See the full SCModeling policy for all 11 tools.

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

ENFORCE ON MY SCMODELING →

View all 11 tools →

These attack patterns abuse exactly the kind of access describe_opt_demo 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 describe_opt_demo only ever does what you allow.

SECURE SCMODELING →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the describe_opt_demo tool do? +

Full detail on one optimization demo — controls, available scenario keys, sites, fixed parameters, citations, and the key finding the demo illustrates. Use this before get_opt_result to know what scenario_key values are accepted.. It is categorised as a Read tool in the SCModeling MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on describe_opt_demo? +

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

What risk level is describe_opt_demo? +

describe_opt_demo is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit describe_opt_demo? +

Yes. Add a rate_limit block to the describe_opt_demo 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 describe_opt_demo completely? +

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

describe_opt_demo is provided by the SCModeling MCP server (https://scmodeling.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SCModeling tool call.

Deterministic rules across all 11 SCModeling 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.