List website status flags used in the website_status_flags search filter.
AI agents call get_website_status_flags to retrieve information from Infobel Api without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves reference data (website status flag definitions) used to filter search queries. It performs no modifications, deletions, executions, or financial operations. The blast radius of misuse is minimal—an AI agent obtaining this reference data poses negligible risk.
From the tool's definition Tool name 'get_website_status_flags' and description 'List website status flags' indicate a retrieval operation with no side effects. The verb 'List' and context of retrieving enumeration values for a search filter confirms read-only behavior.
Attacks that exploit this kind of access
List website status flags used in the website_status_flags search filter. It is categorised as a Read tool in the Infobel Api MCP Server, which means it retrieves data without modifying state.
Register the Infobel Api MCP server in PolicyLayer and add a rule for get_website_status_flags: 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 Infobel Api. Nothing to install.
get_website_status_flags 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 get_website_status_flags 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 get_website_status_flags. 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.
get_website_status_flags is provided by the Infobel Api MCP server (techinfobel/infobel-getdata-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →