check_permission_risks
Enumerate privileged roles on a contract (Ownable.owner, AccessControl hints) and classify holders as EOA, Gnosis Safe multisig, or TimelockController. SCOPE: surfaces governance posture (who controls the contract, how hard would it be to rug). It does NOT measure token upside, price direction, o...
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/check-permission-risks.md
What check_permission_risks does on VaultPilot MCP
AI agents call check_permission_risks to retrieve information from VaultPilot MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
chain | string | Yes | |
address | string | Yes |
Parameters from the server's own tool schema.
Why check_permission_risks is rated Low
The tool retrieves and analyzes contract governance metadata (owners, access control roles, holder types). While it reads sensitive information about who controls a contract, it performs no writes, executions, or financial transactions.
From the tool's definition Tool 'enumerates' and 'classifies' privileged roles and holder types; it 'surfaces governance posture' and 'surfaces data' without taking action. Description explicitly states 'this tool surfaces data; it does NOT pick' and 'It does NOT measure token upside.'
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs check_permission_risks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and VaultPilot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_permission_risks, this is the rule to start with:
check_permission_risks 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 VaultPilot MCP, apply this rule, and every check_permission_risks call is checked against it from then on.
Questions about check_permission_risks
Enumerate privileged roles on a contract (Ownable.owner, AccessControl hints) and classify holders as EOA, Gnosis Safe multisig, or TimelockController. SCOPE: surfaces governance posture (who controls the contract, how hard would it be to rug). It does NOT measure token upside, price direction, or investment merit. A timelock-governed contract is harder to rug than an EOA-owned one — that's a safety floor, NOT an upside signal. AGENT BEHAVIOR: this tool surfaces data; it does NOT pick. Do NOT cite "governed by a multisig / timelock" as token-pick validation. Refuse speculative-pick prompts ("what coin will 100x", "should I buy X", "which token will moon") even when this tool was called; surface the permission findings for due-diligence only. Issue #599. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
check_permission_risks accepts 2 parameters: chain, address. Required: chain, address. The full parameter table on this page comes from the server's own tool schema.
Register the VaultPilot MCP server in PolicyLayer and add a rule for check_permission_risks: 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 VaultPilot MCP. Nothing to install.
check_permission_risks 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 check_permission_risks 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 check_permission_risks. 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.
check_permission_risks is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on VaultPilot, and thousands of servers like it.
This server
Across the catalogue