create_blog_author
Create a new author for blog articles. Returns an authorId that can be used in generate_blog_post and update_blog_article.
This record as markdown: /tools/io-github-bitsandtea-postking-mcp/create-blog-author.md
What create_blog_author does on Postking Mcp
AI agents use create_blog_author 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 create_blog_author is rated Medium
This tool creates new data (author records) in a reversible manner. It does not execute arbitrary code, delete data, move money, or have destructive side effects. Creating an author record is a standard Write operation. Severity is medium because misuse could result in spam authors or polluted author metadata, but the impact is limited to blog metadata and can be remediated by deletion.
From the tool's definition Tool description explicitly states 'Create a new author', which is a data creation operation. The tool generates and returns an authorId for use in subsequent blog operations.
Attacks that exploit this kind of access
The rule that runs create_blog_author 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 create_blog_author, this is the rule to start with:
create_blog_author 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 create_blog_author call is checked against it from then on.
Questions about create_blog_author
Create a new author for blog articles. Returns an authorId that can be used in generate_blog_post and update_blog_article. 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 create_blog_author: 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.
create_blog_author 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 create_blog_author 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 create_blog_author. 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.
create_blog_author 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