decide_command_center_item

SERVERFreedom Mcp SOURCEhttps://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp

High RISK CLASS

Category Execute

Parameters 63 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-getfreedomos-freedom-mcp/decide-command-center-item.md

WHAT IT DOES

What decide_command_center_item does on Freedom Mcp

AI agents invoke decide_command_center_item to trigger actions in Freedom Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`revise`	boolean	—	revise:true with decision:"denied" sends the card back to the producing agent to redo with your feedback (feedback required in that case) — nothing publishes. R
`item_id`	string	Yes	UUID of the Command Center card to decide on
`decision`	string	Yes	The decision: approved, denied, snoozed, or dismissed (dismissed = honest acknowledgment of a blocked_on_you card — never resolves it)
`feedback`	string	—	Optional feedback, especially important for denials. Be specific.
`companyId`	string	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`grant_mode`	string	—	Capability-approval (mcp_tool_call) cards only: 'once' runs the approved call WITHOUT granting the capability for future calls (the next identical call asks aga

Parameters from the server's own tool schema.

RISK

Why decide_command_center_item is rated High

Triggers a complex multi-step automated pipeline with broad downstream effects on agent behavior.

From the tool's definition processes decision through full approval pipeline, initiates multi-step agent process

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs decide_command_center_item safely

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

decide_command_center_item Rate-limited

decide_command_center_item stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "decide_command_center_item": {
      "limits": [
        {
          "counter": "decide_command_center_item_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about decide_command_center_item

What does the decide_command_center_item tool do? +

Approve or deny a Command Center card. This processes the decision through the full approval pipeline including trust scoring, autopilot evaluation, skill learning, and deliverable queue progression. [sensitive-tier, initiates a multi-step agent process — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.]. It is categorised as a Execute tool in the Freedom Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does decide_command_center_item accept? +

decide_command_center_item accepts 6 parameters: revise, item_id, decision, feedback, companyId, grant_mode. Required: item_id, decision, companyId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on decide_command_center_item? +

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

What risk level is decide_command_center_item? +

decide_command_center_item is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit decide_command_center_item? +

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

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

decide_command_center_item is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Freedom, and thousands of servers like it.

This server

All 238 Freedom tools → High-risk tools on this server →

Across the catalogue

adb_shell_command on Android Forensics ADB MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →