scan_contract_source
pactlint: Scan Solidity source code for security bugs before you deploy, review or depend on it. For a deployed verified contract use scan_contract_address. Runs solc, Slither and custom DeFi detectors (unchecked ERC-20 returns, zero slippage limits, oracle misuse, ERC-4626 inflation, signature r...
This record as markdown: /tools/dev-tanod-tanod/scan-contract-source.md
What scan_contract_source does on Tanod
AI agents call scan_contract_source to retrieve information from Tanod 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 |
|---|---|---|---|
source | object | — | A single Solidity file (no imports; at most 200 KB). Give either source or standard_json. |
filename | string | — | File name for `source` (ends in .sol; default Contract.sol); findings cite it in file:line. |
include_noisy | boolean | — | Also report detectors dropped by default as noisy (high false-positive rate); default false. |
standard_json | object | — | solc standard-JSON input with inline 'content' for every file (at most 1 MB and 500 files). |
compiler_version | object | — | Exact solc version (default: from pragma). |
include_dependencies | boolean | — | Also report findings in dependencies, tests and mocks (lib/, node_modules/, OpenZeppelin, ...); default false. |
include_informational | boolean | — | Also report informational (style and best-practice) findings; default false. |
Parameters from the server's own tool schema.
Why scan_contract_source is rated Low
Even though scan_contract_source only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts file system path (filename)
Attacks that exploit this kind of access
The rule that runs scan_contract_source safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scan_contract_source, this is the rule to start with:
scan_contract_source 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 Tanod, apply this rule, and every scan_contract_source call is checked against it from then on.
Questions about scan_contract_source
pactlint: Scan Solidity source code for security bugs before you deploy, review or depend on it. For a deployed verified contract use scan_contract_address. Runs solc, Slither and custom DeFi detectors (unchecked ERC-20 returns, zero slippage limits, oracle misuse, ERC-4626 inflation, signature replay, ...). Returns a JSON report (findings with severity, confidence, file:line and a fix) plus Markdown. Price: USD 0.25 up to 3,000 nSLOC, USD 0.75 up to 15,000; refused inputs are never charged. Free: 3 scans or 30 txpeek checks per IP per UTC day. Typically 1-5 s, up to about 30 s for a large project; at most 60 s; a full queue is a 503 with Retry-After (not charged). Automated and heuristic, not an audit: findings can be false positives and an empty report does not prove the code is free of bugs. Docs: https://tanod.dev/learn/smart-contract-scanner-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
scan_contract_source accepts 7 parameters: source, filename, include_noisy, standard_json, compiler_version, include_dependencies, include_informational. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for scan_contract_source: 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 Tanod. Nothing to install.
scan_contract_source 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 scan_contract_source 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 scan_contract_source. 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.
scan_contract_source is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue