AI agents use reject_spec_proposal to create or update resources in Scrumdo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Scrumdo environment.
This tool modifies project management data by changing a specification proposal's status from pending to rejected. This is a Write operation because it creates or modifies data reversibly—proposals can be resubmitted or status can be changed. It lacks the irreversibility of Destructive actions or the external execution characteristics of Execute tools.
From the tool's definition Tool name 'reject_spec_proposal' indicates modification of proposal status. Sibling tools like 'accept_spec_proposal', 'add_comment', 'add_card_label', and 'assign_card' are all Write operations that modify ScrumDo board state.
Attacks that exploit this kind of access
reject_spec_proposal. It is categorised as a Write tool in the Scrumdo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Scrumdo MCP server in PolicyLayer and add a rule for reject_spec_proposal: 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 Scrumdo. Nothing to install.
reject_spec_proposal is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the reject_spec_proposal 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.
Set action: deny in the PolicyLayer policy for reject_spec_proposal. 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.
reject_spec_proposal is provided by the Scrumdo MCP server (scrumdollc/scrumdo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →