record_indicator_reading
Append a reading to an indicator: the value observed, optionally the value the plan EXPECTED by that date (this is what turns a reading into on_track / off_track), when it was observed (defaults to now), and the source it was read from. Readings are appended, never edited — a wrong reading is cor...
This record as markdown: /tools/adrata-adrata-mcp/record-indicator-reading.md
What record_indicator_reading does on Adrata
AI agents call record_indicator_reading to retrieve information from Adrata without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why record_indicator_reading is rated Low
Even though record_indicator_reading only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs record_indicator_reading safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adrata, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For record_indicator_reading, this is the rule to start with:
record_indicator_reading 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 Adrata, apply this rule, and every record_indicator_reading call is checked against it from then on.
Questions about record_indicator_reading
Append a reading to an indicator: the value observed, optionally the value the plan EXPECTED by that date (this is what turns a reading into on_track / off_track), when it was observed (defaults to now), and the source it was read from. Readings are appended, never edited — a wrong reading is corrected by a new reading with a note. Each call adds one row; do not retry with a fresh idempotencyKey.${GOVERNED_NOTE}. It is categorised as a Read tool in the Adrata MCP Server, which means it retrieves data without modifying state.
Register the Adrata MCP server in PolicyLayer and add a rule for record_indicator_reading: 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 Adrata. Nothing to install.
record_indicator_reading 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 record_indicator_reading 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 record_indicator_reading. 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.
record_indicator_reading is provided by the Adrata MCP server (@adrata/adrata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adrata, and thousands of servers like it.
This server
Across the catalogue