record_role_access
Record whether a role can reach a given endpoint, for cross-role comparison.
This record as markdown: /tools/intellirecon-console/record-role-access.md
What record_role_access does on Intellirecon Console
AI agents use record_role_access 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_role_access is rated Medium
This tool records (writes) role-to-endpoint access data persistently so it can be compared across roles. It does not delete data, execute commands, or involve financial transactions. It is a Write operation that stores reconnaissance/audit findings. Misuse could lead to falsified access control records or misleading security assessments, giving it medium severity.
From the tool's definition 'Record whether a role can reach a given endpoint' — the tool writes/stores access control findings for roles and endpoints into a data store for later cross-role comparison.
Attacks that exploit this kind of access
The rule that runs record_role_access 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_role_access, this is the rule to start with:
record_role_access 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_role_access call is checked against it from then on.
Questions about record_role_access
Record whether a role can reach a given endpoint, for cross-role comparison. 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_role_access: 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_role_access 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_role_access 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_role_access. 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_role_access 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