# get_contract_roles

A read tool on the Token Info MCP Server MCP server.

Agent View of the PolicyLayer registry record for `get_contract_roles`. HTML page: https://policylayer.com/tools/0xwuchuan-token-info-mcp/get-contract-roles

## Facts

- Tool: `get_contract_roles`
- Server: Token Info MCP Server (`0xwuchuan/token-info-mcp`) — https://policylayer.com/tools/0xwuchuan-token-info-mcp.md
- Homepage: https://github.com/0xwuchuan/token-info-mcp
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_contract_roles",
    "arguments": {}
  }
}
```

## Why get_contract_roles is rated Low

This tool appears to retrieve role information from smart contracts, which is a read-only operation. The empty description and generic name 'get_contract_roles' are consistent with querying contract state. Given the server's focus on 'comprehensive smart contract analysis' (passive intelligence gathering), this fits the Read category.

From the tool's own definition: "Tool name 'get_contract_roles' and server description indicating 'OpenZeppelin AccessControl role management' analysis suggests retrieving/querying contract role information. No side effects, modifications, or external operations described."

## Use case

AI agents call get_contract_roles to retrieve information from Token Info MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Token Info MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_contract_roles": {}
  }
}
```

## Other tools on Token Info MCP Server (2)

- `check_address_type` — Read — https://policylayer.com/tools/0xwuchuan-token-info-mcp/check-address-type.md
- `get_proxy_admin` — Read — https://policylayer.com/tools/0xwuchuan-token-info-mcp/get-proxy-admin.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0xwuchuan-token-info-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xwuchuan-token-info-mcp