This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/check-website.md
What check_website does on Sequenzy Mcp
AI agents call check_website to retrieve information from Sequenzy Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_website is rated Low
This tool performs a read-only operation to retrieve or verify sending domain configuration details. There are no side effects, data modifications, or destructive actions. The low severity reflects minimal risk even if misused, as it only exposes existing domain configuration data without the ability to modify or delete information.
From the tool's definition Tool name 'check_website' and description 'Read a sending domain' explicitly indicate retrieval of domain information without modification.
Attacks that exploit this kind of access
The rule that runs check_website safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sequenzy Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_website, this is the rule to start with:
check_website 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 Sequenzy Mcp, apply this rule, and every check_website call is checked against it from then on.
Questions about check_website
Read a sending domain. It is categorised as a Read tool in the Sequenzy Mcp MCP Server, which means it retrieves data without modifying state.
Register the Sequenzy MCP server in PolicyLayer and add a rule for check_website: 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 Sequenzy Mcp. Nothing to install.
check_website 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_website 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_website. 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_website is provided by the Sequenzy MCP server (Sequenzy/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sequenzy, and thousands of servers like it.
This server
Across the catalogue