create_monitor

SERVERMeta Council SOURCEhttps://meta-council.com/mcp

Medium RISK CLASS

Category Write

Parameters 85 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-meta-council-decision-intelligence/create-monitor.md

WHAT IT DOES

What create_monitor does on Meta Council

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

Parameter	Type	Required	Description
`name`	string	Yes	Human label for the watch, e.g. 'Backlog over 50'.
`action`	string	Yes	What to do when the condition holds.
`subject`	string	Yes	Which of your counts to watch.
`threshold`	integer	Yes	The line the count must cross.
`comparator`	string	Yes	How the count is compared against threshold.
`action_config`	object	—	Settings for the chosen action. start_workflow needs workflow_slug; notify_slack needs message.
`status_filter`	string	—	Optional: count only rows in this status, e.g. 'todo'. Omit to count them all.
`cooldown_seconds`	integer	—	Minimum gap between firings. Defaults to 3600. Values below one scheduler tick are raised to 60, and the stored value reflects that.

Parameters from the server's own tool schema.

RISK

Why create_monitor is rated Medium

An AI agent can call create_monitor faster than any human can review: one bad instruction and it creates or modifies resources in Meta Council by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (11 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_monitor safely

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

create_monitor Rate-limited

create_monitor 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": {
    "create_monitor": {
      "limits": [
        {
          "counter": "create_monitor_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 Meta Council, apply this rule, and every create_monitor call is checked against it from then on.

FAQ

Questions about create_monitor

What does the create_monitor tool do? +

Save a standing watch that fires later, on its own: when a count you name crosses a line you set, do the thing you chose. Lets an agent bank a condition and stop polling for it. The watch survives the conversation that created it. Note that start_workflow spends the account's credits unattended each time it fires, so the cooldown is the only thing bounding what it costs. Requires authentication, a Pro or Enterprise account, and the monitors:write scope. It is categorised as a Write tool in the Meta Council MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does create_monitor accept? +

create_monitor accepts 8 parameters: name, action, subject, threshold, comparator, action_config, status_filter, cooldown_seconds. Required: name, action, subject, threshold, comparator. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_monitor? +

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

What risk level is create_monitor? +

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

Can I rate-limit create_monitor? +

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

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

create_monitor is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meta Council, and thousands of servers like it.

This server

All 280 Meta Council tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

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