get_sprint_item_pointers
[SUPPORT] 2976e168 — list the GENERIC POINTERS attached to a sprint item (oldest first). Each pointer is {id, source_type, targets:[{uri, selector, subSelector?}], label, created_at} — the stored shape with its JSON targets deserialized. Read-only; does NOT resolve the targets (use resolve_sprint...
This record as markdown: /tools/io-github-ajc3xc-meridian/get-sprint-item-pointers.md
What get_sprint_item_pointers does on Meridian
AI agents call get_sprint_item_pointers to retrieve information from Meridian without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | — | |
project_name | string | — | Project name — an alternative to project_id; resolved to the id internally. project_id wins if both are given. |
sprint_item_id | string | Yes | The sprint item whose pointers to list. |
Parameters from the server's own tool schema.
Why get_sprint_item_pointers is rated Low
This tool retrieves and lists pointer metadata associated with sprint items. It performs a query operation that returns data without modifying, creating, or deleting any state. The explicit 'Read-only' designation and the function of listing/retrieving existing pointers confirm the Read category. Low severity because access to sprint item metadata poses minimal risk even if misused.
From the tool's definition Tool description explicitly states 'Read-only; does NOT resolve the targets'. It 'list[s] the GENERIC POINTERS attached to a sprint item' and returns stored metadata about pointers (id, source_type, targets, label, created_at).
Attacks that exploit this kind of access
The rule that runs get_sprint_item_pointers 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 get_sprint_item_pointers, this is the rule to start with:
get_sprint_item_pointers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meridian, apply this rule, and every get_sprint_item_pointers call is checked against it from then on.
Questions about get_sprint_item_pointers
[SUPPORT] 2976e168 — list the GENERIC POINTERS attached to a sprint item (oldest first). Each pointer is {id, source_type, targets:[{uri, selector, subSelector?}], label, created_at} — the stored shape with its JSON targets deserialized. Read-only; does NOT resolve the targets (use resolve_sprint_item_pointers for that). It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
get_sprint_item_pointers accepts 3 parameters: project_id, project_name, sprint_item_id. Required: sprint_item_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 get_sprint_item_pointers: 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.
get_sprint_item_pointers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_sprint_item_pointers 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 get_sprint_item_pointers. 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.
get_sprint_item_pointers 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.
This server
Across the catalogue