scrape_substack
Scrape Substack publication metadata + recent posts. Use for newsletter-research agents. Example call: {"publication": "platformer"} Cost: $0.005–$0.05 USDC on Base per call.
This record as markdown: /tools/io-github-colinhughes2121-gocreative-agent-api/scrape-substack.md
What scrape_substack does on GoCreative Agent API
AI agents call scrape_substack to retrieve information from GoCreative Agent API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
publication | string | Yes |
Parameters from the server's own tool schema.
Why scrape_substack is rated Low
This tool retrieves and queries publicly available Substack publication data (metadata and posts). It has no capability to modify, delete, execute code, or perform financial transactions. The blast radius of misuse is minimal—an agent could retrieve unwanted metadata or harvest public newsletter information, but cannot alter data or trigger harmful operations. Categorized as Read with low severity.
From the tool's definition Tool name 'scrape_substack' and description 'Scrape Substack publication metadata + recent posts' clearly indicate data retrieval with no modification, deletion, or side effects. The example call retrieves publicly available newsletter information.
Attacks that exploit this kind of access
The rule that runs scrape_substack safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GoCreative Agent API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scrape_substack, this is the rule to start with:
scrape_substack 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 GoCreative Agent API, apply this rule, and every scrape_substack call is checked against it from then on.
Questions about scrape_substack
Scrape Substack publication metadata + recent posts. Use for newsletter-research agents. Example call: {"publication": "platformer"} Cost: $0.005–$0.05 USDC on Base per call. It is categorised as a Read tool in the GoCreative Agent API MCP Server, which means it retrieves data without modifying state.
scrape_substack accepts 1 parameter: publication. Required: publication. The full parameter table on this page comes from the server's own tool schema.
Register the GoCreative Agent API MCP server in PolicyLayer and add a rule for scrape_substack: 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 GoCreative Agent API. Nothing to install.
scrape_substack 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 scrape_substack 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 scrape_substack. 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.
scrape_substack is provided by the GoCreative Agent API MCP server (https://api.gocreativeai.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GoCreative Agent API, and thousands of servers like it.
This server
Across the catalogue