New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

polygon_contract

Whether a polygon address is a contract, bytecode size, and ERC-20 metadata if applicable. Pay-per-call ($0.01 USDC).

SERVER47620 Evm SOURCE47620-evm-mcp
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/47620-evm-mcp/polygon-contract.md

What polygon_contract does on 47620 Evm

AI agents call polygon_contract to retrieve information from 47620 Evm without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
address string Yes polygon address (0x...)

Parameters from the server's own tool schema.

Why polygon_contract is rated Low

Even though polygon_contract 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.

Questions about polygon_contract

What does the polygon_contract tool do? +

Whether a polygon address is a contract, bytecode size, and ERC-20 metadata if applicable. Pay-per-call ($0.01 USDC). It is categorised as a Read tool in the 47620 Evm MCP Server, which means it retrieves data without modifying state.

What parameters does polygon_contract accept? +

polygon_contract accepts 1 parameter: address. Required: address. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on polygon_contract? +

Register the 47620 Evm MCP server in PolicyLayer and add a rule for polygon_contract: 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 47620 Evm. Nothing to install.

What risk level is polygon_contract? +

polygon_contract is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit polygon_contract? +

Yes. Add a rate_limit block to the polygon_contract 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.

How do I block polygon_contract completely? +

Set action: deny in the PolicyLayer policy for polygon_contract. 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.

What MCP server provides polygon_contract? +

polygon_contract is provided by the 47620 Evm MCP server (47620-evm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on 47620 Evm, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 47620 Evm's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.