AI agents call schema to retrieve information from Scrapegraph without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'schema' suggests it retrieves metadata or structural information about available operations or data formats on the scraping service. This is a read-only operation with minimal side effects. However, confidence is moderate due to lack of explicit description. The low severity reflects typical read operations that query data without modifying state or executing external commands.
From the tool's definition Tool name 'schema' on a scraping server typically retrieves schema/structure information. No description provided, limiting certainty.
Documented attack patterns abuse exactly the kind of access schema gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Scrapegraph, and nothing reaches the server without passing your rules. This is the rule we recommend for schema:
{
"version": "1",
"default": "deny",
"tools": {
"schema": {}
}
}schema is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
schema. It is categorised as a Read tool in the Scrapegraph MCP Server, which means it retrieves data without modifying state.
Register the Scrapegraph MCP server in PolicyLayer and add a rule for schema: 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 Scrapegraph. Nothing to install.
schema 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 schema 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 schema. 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.
schema is provided by the Scrapegraph MCP server (ScrapeGraphAI/scrapegraph-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Scrapegraph, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Scrapegraph tools catalogued and risk-classified — across an index of 43,000+ MCP servers.