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

verify_check_site

Run a pre-launch QA check on a live site: real Chromium on desktop + mobile, HTTP status, broken links, title/meta/H1, Open Graph, mobile overflow, console errors, screenshots. Uses today

SERVER6frame Verify SOURCEbret1976/6frame-verify
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade A, identity unverified Pull the record →

This record as markdown: /tools/6frame-verify/verify-check-site.md

What verify_check_site does on 6frame Verify

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

Why verify_check_site is rated Low

Even though verify_check_site 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 verify_check_site

What does the verify_check_site tool do? +

Run a pre-launch QA check on a live site: real Chromium on desktop + mobile, HTTP status, broken links, title/meta/H1, Open Graph, mobile overflow, console errors, screenshots. Uses today. It is categorised as a Read tool in the 6frame Verify MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on verify_check_site? +

Register the 6frame Verify MCP server in PolicyLayer and add a rule for verify_check_site: 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 6frame Verify. Nothing to install.

What risk level is verify_check_site? +

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

Can I rate-limit verify_check_site? +

Yes. Add a rate_limit block to the verify_check_site 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 verify_check_site completely? +

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

verify_check_site is provided by the 6frame Verify MCP server (bret1976/6frame-verify). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on 6frame Verify, 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 6frame Verify'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.