update_proposal_status · Ebony Enriching MCP: Risk & Policy

WHAT IT DOES

What update_proposal_status does on Ebony Enriching

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

WHY IT NEEDS A POLICY

Why update_proposal_status needs a policy

This tool creates or modifies data reversibly by updating the status of a proposal. It falls under the Write category because it changes existing data without irreversible deletion. Severity is medium because misuse could corrupt research workflow state, but the append-only semantics and the nature of status updates (typically not causing financial or destructive effects) limit the blast radius.

From the tool's definition Tool name is 'update_proposal_status' and description states 'Update a proposal'. The server uses 'append-only semantics' and 'filesystem storage', indicating that updates modify existing data but do not permanently delete or destroy it.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_proposal_status Rate-limited

update_proposal_status 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": {
    "update_proposal_status": {
      "limits": [
        {
          "counter": "update_proposal_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about update_proposal_status

What does the update_proposal_status tool do? +

Update a proposal. It is categorised as a Write tool in the Ebony Enriching MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_proposal_status? +

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

What risk level is update_proposal_status? +

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

Can I rate-limit update_proposal_status? +

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

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

update_proposal_status is provided by the Ebony Enriching MCP server (parkviewlab/ebony-enriching). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.