AI agents call credits 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.
This tool retrieves account credit balance information. It performs a simple data lookup without modifying, executing, or deleting anything. The blast radius of misuse is minimal—an agent could only learn the remaining credits, which is low-impact information disclosure.
From the tool's definition Tool name 'credits' and description 'Return remaining API credits' indicates a query/retrieval operation with no side effects. The API endpoint reference (GET /credits) confirms it uses HTTP GET, which is idempotent and read-only.
Documented attack patterns abuse exactly the kind of access credits 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 credits:
{
"version": "1",
"default": "deny",
"tools": {
"credits": {}
}
}credits 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.
Return remaining API credits (API v2 GET /credits). 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 credits: 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.
credits 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 credits 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 credits. 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.
credits 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.