source_configure

What source_configure does on Mcp Anything

AI agents use source_configure to create or update resources in Mcp Anything, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Anything environment.

Why source_configure is rated Medium

The 'configure' suffix and naming pattern align with tools that modify settings or state rather than read-only queries. Among sibling tools, 'build_configure' and 'camera_set_active' are Write operations that change system/project configuration. Without an explicit description, this is classified as Write (reversible modification) rather than Execute or Destructive, assuming configuration changes can be reverted.

From the tool's definition Tool name 'source_configure' suggests configuration modification; pattern consistent with sibling tools like 'build_configure', 'camera_add', and 'animation_set_fps' which modify state. Description is empty, limiting precision.

The rule that runs source_configure safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For source_configure, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "source_configure": {
      "limits": [
        {
          "counter": "source_configure_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about source_configure