civitae_vote · Signomy MCP: Risk & Policy

WHAT IT DOES

What civitae_vote does on Signomy

AI agents invoke civitae_vote to trigger actions in Signomy. 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.

WHY IT NEEDS A POLICY

Why civitae_vote needs a policy

Casting a vote is an external operation with real-world governance consequences. It triggers a state change in the governance system (weighted vote recorded), which may affect mission slots, revenue distribution, or constitutional rules. This is not merely writing reversible data — it executes a governance action.

From the tool's definition Cast a weighted vote in a governance session

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

civitae_vote Rate-limited

civitae_vote 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": {
    "civitae_vote": {
      "limits": [
        {
          "counter": "civitae_vote_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Signomy, so you can run agents against it safely.

FAQ

Questions about civitae_vote

What does the civitae_vote tool do? +

Cast a weighted vote in a governance session. It is categorised as a Execute tool in the Signomy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on civitae_vote? +

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

What risk level is civitae_vote? +

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

Can I rate-limit civitae_vote? +

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

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

civitae_vote is provided by the Signomy MCP server (sunrisesillneversee/agent-universe). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.