delete_sprint_item_pointer
[MAINTENANCE] 2976e168 — delete ONE generic pointer from a sprint item by its pointer id (the id returned by add_sprint_item_pointer / get_sprint_item_pointers). A stored pointer is immutable, so 'editing' one is delete-then-re-add. Idempotent: returns {pointer_id, deleted:false} when no pointer ...
This record as markdown: /tools/io-github-ajc3xc-meridian/delete-sprint-item-pointer.md
What delete_sprint_item_pointer does on Meridian
AI agents call delete_sprint_item_pointer to permanently remove resources in Meridian, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
pointer_id | string | Yes | The id of the pointer to delete. |
Parameters from the server's own tool schema.
Why delete_sprint_item_pointer is rated Critical
The tool irreversibly deletes data (a sprint item pointer) and cannot be undone without manual re-addition. While marked [MAINTENANCE] and idempotent, it still performs a destructive operation on persistent state. The high severity reflects that deleting pointers could break task coordination workflows in AI coding sessions, and the tool operates on shared persistent memory.
From the tool's definition delete ONE generic pointer from a sprint item by its pointer id... A stored pointer is immutable, so 'editing' one is delete-then-re-add.
Attacks that exploit this kind of access
The rule that runs delete_sprint_item_pointer safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meridian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_sprint_item_pointer, this is the rule to start with:
delete_sprint_item_pointer is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Meridian, apply this rule, and every delete_sprint_item_pointer call is checked against it from then on.
Questions about delete_sprint_item_pointer
[MAINTENANCE] 2976e168 — delete ONE generic pointer from a sprint item by its pointer id (the id returned by add_sprint_item_pointer / get_sprint_item_pointers). A stored pointer is immutable, so 'editing' one is delete-then-re-add. Idempotent: returns {pointer_id, deleted:false} when no pointer had that id, rather than erroring. Persistent-state disclosure: on hosted Meridian, supplied text and project/session metadata are sent to and stored in Meridian's service; self-hosted deployments keep them in the configured local SQLite/Postgres database. This data is visible in the dashboard/API and later project context or handoffs. Delete individual tasks, notes, or decisions where supported, or delete the project/account using the documented controls. Do not include secrets. It is categorised as a Destructive tool in the Meridian MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_sprint_item_pointer accepts 1 parameter: pointer_id. Required: pointer_id. The full parameter table on this page comes from the server's own tool schema.
Register the Meridian MCP server in PolicyLayer and add a rule for delete_sprint_item_pointer: 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 Meridian. Nothing to install.
delete_sprint_item_pointer is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_sprint_item_pointer 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 delete_sprint_item_pointer. 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.
delete_sprint_item_pointer is provided by the Meridian MCP server (@meridianmcp/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meridian, and thousands of servers like it.
Across the catalogue