config.set

Update bot configuration at runtime. Supports daily_budget (max USDC per day) and min_conviction (minimum trade size to copy). Changes take effect immediately and persist across restarts.

SERVERPolymarket Agent Mcp SOURCEdemwick/polymarket-agent-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/demwick-polymarket-agent-mcp/config.set.md

WHAT IT DOES

What config.set does on Polymarket Agent Mcp

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

RISK

Why config.set is rated Medium

Modifies reversible trading bot configuration settings with financial impact via budget controls.

From the tool's definition Update bot configuration at runtime, daily_budget, min_conviction, changes persist

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs config.set safely

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

config.set Rate-limited

config.set stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "config.set": {
      "limits": [
        {
          "counter": "config.set_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Polymarket Agent Mcp, apply this rule, and every config.set call is checked against it from then on.

FAQ

Questions about config.set

What does the config.set tool do? +

Update bot configuration at runtime. Supports daily_budget (max USDC per day) and min_conviction (minimum trade size to copy). Changes take effect immediately and persist across restarts. It is categorised as a Write tool in the Polymarket Agent Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on config.set? +

Register the Polymarket Agent MCP server in PolicyLayer and add a rule for config.set: 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 Polymarket Agent Mcp. Nothing to install.

What risk level is config.set? +

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

Can I rate-limit config.set? +

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

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

config.set is provided by the Polymarket Agent MCP server (demwick/polymarket-agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Polymarket Agent, and thousands of servers like it.

This server

All 48 Polymarket Agent tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →