site_blog_post · Yaver MCP: Risk & Policy

WHAT IT DOES

What site_blog_post does on Yaver

AI agents use site_blog_post to create or update resources in Yaver — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.

PARAMETERS

Parameter	Type	Required
`tags`	array	—
`draft`	boolean	—
`title`	string	Yes
`content`	string	—

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why site_blog_post needs a policy

An AI agent can call site_blog_post faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.

Risk signalsAccepts raw HTML/template content (content)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

site_blog_post Rate-limited

site_blog_post 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "site_blog_post": {
      "limits": [
        {
          "counter": "site_blog_post_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Yaver, so you can run agents against it safely.

FAQ

Questions about site_blog_post

What does the site_blog_post tool do? +

Create a blog post. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does site_blog_post accept? +

site_blog_post accepts 4 parameters: tags, draft, title, content. Required: title. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on site_blog_post? +

Register the Yaver MCP server in PolicyLayer and add a rule for site_blog_post: 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 Yaver. Nothing to install.

What risk level is site_blog_post? +

site_blog_post is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit site_blog_post? +

Yes. Add a rate_limit block to the site_blog_post 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.

How do I block site_blog_post completely? +

Set action: deny in the PolicyLayer policy for site_blog_post. 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.

What MCP server provides site_blog_post? +

site_blog_post is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.