import_blog_articles
Import articles from an external blog, RSS feed, or Blogger URL into a PostKing publication as drafts. Returns id+title+slug by default (short); use detail=
This record as markdown: /tools/io-github-bitsandtea-postking-mcp/import-blog-articles.md
What import_blog_articles does on Postking Mcp
AI agents use import_blog_articles to create or update resources in Postking Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Postking Mcp environment.
Why import_blog_articles is rated Medium
The tool creates or modifies data (import and draft creation) without permanent deletion or irreversible consequences. This falls squarely into the Write category. Severity is medium because an agent could import large volumes of unvetted or malicious content into the user's publication, requiring manual review and cleanup.
From the tool's definition Tool description states it will 'Import articles...into a PostKing publication as drafts,' which creates new draft content objects in the system.
Attacks that exploit this kind of access
The rule that runs import_blog_articles safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Postking Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For import_blog_articles, this is the rule to start with:
import_blog_articles stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Postking Mcp, apply this rule, and every import_blog_articles call is checked against it from then on.
Questions about import_blog_articles
Import articles from an external blog, RSS feed, or Blogger URL into a PostKing publication as drafts. Returns id+title+slug by default (short); use detail=. It is categorised as a Write tool in the Postking Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Postking MCP server in PolicyLayer and add a rule for import_blog_articles: 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 Postking Mcp. Nothing to install.
import_blog_articles is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the import_blog_articles 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 import_blog_articles. 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.
import_blog_articles is provided by the Postking MCP server (postking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Postking, and thousands of servers like it.
This server
Across the catalogue