link_flag_to_section
[MAINTENANCE] 8ca89e8f — DURABLY link a docx section/paragraph/figure/table (any doc_elements id — the same id space index_figure/index_table/link_figure_caption already anchor to) to the config-flag state that produced its underlying numbers. This is the check that catches 'results computed with...
This record as markdown: /tools/io-github-ajc3xc-meridian/link-flag-to-section.md
What link_flag_to_section does on Meridian
AI agents use link_flag_to_section to create or update resources in Meridian, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meridian environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
doc | string | Yes | The stored document's source (the path/URL you ingested it under via ingest_document). |
value | object | Yes | The value the flag actually had when this section's numbers were produced (any JSON scalar — string/number/boolean/null). |
default | object | — | The flag's default AS RECORDED by get_flag_registry at link time — what a later get_flag_drift compares the current codebase default against. Optional but recom |
flag_name | string | Yes | The config flag's name (as scanned by get_flag_registry, e.g. 'DT_ONLY_WIDTH'). |
element_id | string | Yes | The doc_elements.id of the section/paragraph/figure/table this flag state applies to. |
project_id | string | — | |
source_file | string | — | Optional: the file the flag was read from (from get_flag_registry's 'file'), pinning drift detection to this exact call site. |
source_line | integer | — | Optional: the line the flag was read at (from get_flag_registry's 'line'), paired with source_file. |
project_name | string | — | Project name — an alternative to project_id; resolved to the id internally. project_id wins if both are given. |
Parameters from the server's own tool schema.
Why link_flag_to_section is rated Medium
The tool persistently writes/creates a linkage record associating document elements with config-flag states. This is a reversible metadata write operation — it stores traceability relationships in a durable store. No code is executed, no data is deleted, and no financial transaction occurs.
From the tool's definition DURABLY link a docx section/paragraph/figure/table ... to the config-flag state that produced its underlying numbers
Attacks that exploit this kind of access
The rule that runs link_flag_to_section 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 link_flag_to_section, this is the rule to start with:
link_flag_to_section 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Meridian, apply this rule, and every link_flag_to_section call is checked against it from then on.
Questions about link_flag_to_section
[MAINTENANCE] 8ca89e8f — DURABLY link a docx section/paragraph/figure/table (any doc_elements id — the same id space index_figure/index_table/link_figure_caption already anchor to) to the config-flag state that produced its underlying numbers. This is the check that catches 'results computed with the wrong flag state, then cited as current' — e.g. a flag that silently skipped a whole code path regardless of another flag, or a stale count cited after a fix superseded it. Typical flow: call get_flag_registry to find the flag's current file/line/default, compute the section, then call this tool with value=the value actually used and default=the default get_flag_registry reported (so get_flag_drift has something to compare the codebase's CURRENT default against later). Insert-only: re-linking the same (element_id, flag_name) pair after a re-verification adds a new history row rather than overwriting the old one. Returns {project_id, document_id, link}. 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 Write tool in the Meridian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
link_flag_to_section accepts 9 parameters: doc, value, default, flag_name, element_id, project_id, source_file, source_line, project_name. Required: doc, value, flag_name, element_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 link_flag_to_section: 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.
link_flag_to_section 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 link_flag_to_section 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 link_flag_to_section. 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.
link_flag_to_section 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