scrape_medium
Scrape a Medium article or user profile (title, claps, text). Use for content-research agents. Example call: {"url_or_user": "@user"} Cost: $0.005–$0.05 USDC on Base per call.
This record as markdown: /tools/io-github-colinhughes2121-gocreative-agent-api/scrape-medium.md
What scrape_medium does on GoCreative Agent API
AI agents call scrape_medium 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 |
|---|---|---|---|
url_or_user | string | Yes |
Parameters from the server's own tool schema.
Why scrape_medium is rated Low
This tool retrieves publicly available data from Medium without modifying, deleting, or executing code. It extracts article metadata and profile information, which is a classic Read operation. The financial cost is a separate concern (API billing) but does not constitute a Financial risk category, which applies to tools that move money or create financial obligations on behalf of the user.
From the tool's definition Tool description: "Scrape a Medium article or user profile (title, claps, text)." The verb "scrape" combined with the retrieval of public metadata (title, claps, text) indicates data retrieval with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs scrape_medium 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_medium, this is the rule to start with:
scrape_medium 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_medium call is checked against it from then on.
Questions about scrape_medium
Scrape a Medium article or user profile (title, claps, text). Use for content-research agents. Example call: {"url_or_user": "@user"} 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_medium accepts 1 parameter: url_or_user. Required: url_or_user. 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_medium: 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_medium 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_medium 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_medium. 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_medium 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