record_client_observation
Record a client-side-only observation (storage key, DOM/feature flag, console warning, cookie).
This record as markdown: /tools/intellirecon-console/record-client-observation.md
What record_client_observation does on Intellirecon Console
AI agents use record_client_observation to create or update resources in Intellirecon Console, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Intellirecon Console environment.
Why record_client_observation is rated Medium
This tool writes/creates a recorded observation entry. It stores reconnaissance findings (client-side artifacts like cookies, DOM flags, storage keys) into some log or data store. This is a reversible write operation with limited blast radius — it records data rather than exfiltrating or destroying it. Severity is low because it only logs observations internally and does not directly harm systems.
From the tool's definition 'Record a client-side-only observation' — creates/stores a new data entry (storage key, DOM/feature flag, console warning, cookie)
Attacks that exploit this kind of access
The rule that runs record_client_observation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Intellirecon Console, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For record_client_observation, this is the rule to start with:
record_client_observation 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 Intellirecon Console, apply this rule, and every record_client_observation call is checked against it from then on.
Questions about record_client_observation
Record a client-side-only observation (storage key, DOM/feature flag, console warning, cookie). It is categorised as a Write tool in the Intellirecon Console MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Intellirecon Console MCP server in PolicyLayer and add a rule for record_client_observation: 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 Intellirecon Console. Nothing to install.
record_client_observation 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 record_client_observation 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_client_observation. 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_client_observation is provided by the Intellirecon Console MCP server (dokotela021/intellirecon-console). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Intellirecon Console, and thousands of servers like it.
This server
Across the catalogue