marvin_mark_done
AI agents use marvin_mark_done to create or update resources in Amazing Marvin MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazing Marvin MCP Server environment.
Marking a task as done is a reversible state change (tasks can typically be unmarked or re-opened in task management systems). This is a write operation—it modifies data but does not delete it, execute arbitrary code, or trigger financial consequences. The reversibility and isolated scope within a single task's status field make this low severity.
From the tool's definition Tool name 'marvin_mark_done' indicates it marks a task as complete/done. Given the sibling tools create tasks (marvin_add_task), retrieve tasks (marvin_get_due_tasks, marvin_get_todays_tasks), and manage tracking (marvin_start_tracking, marvin_stop_tracking),…
Attacks that exploit this kind of access
marvin_mark_done. It is categorised as a Write tool in the Amazing Marvin MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Amazing Marvin MCP Server MCP server in PolicyLayer and add a rule for marvin_mark_done: 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 Amazing Marvin MCP Server. Nothing to install.
marvin_mark_done 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 marvin_mark_done 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 marvin_mark_done. 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.
marvin_mark_done is provided by the Amazing Marvin MCP Server MCP server (lucadeleo/amazing-marvin-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 →