record_third_party
Record a third-party origin the target depends on (CDN, storage bucket, SaaS API, OAuth provider, ...).
This record as markdown: /tools/intellirecon-console/record-third-party.md
What record_third_party does on Intellirecon Console
AI agents use record_third_party 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_third_party is rated Medium
The tool creates/stores a record of a third-party dependency. This is a Write operation — it adds data to a reconnaissance dataset reversibly. No code execution, deletion, or financial action is involved. Severity is medium because within a security recon context, cataloguing third-party origins could inform subsequent attack planning, but the tool itself only writes metadata.
From the tool's definition Record a third-party origin the target depends on (CDN, storage bucket, SaaS API, OAuth provider, ...)
Attacks that exploit this kind of access
The rule that runs record_third_party 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_third_party, this is the rule to start with:
record_third_party 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_third_party call is checked against it from then on.
Questions about record_third_party
Record a third-party origin the target depends on (CDN, storage bucket, SaaS API, OAuth provider, ...). 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_third_party: 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_third_party 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_third_party 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_third_party. 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_third_party 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