storyline_confirm_brief

A write tool on the Postking MCP server.

SERVERPostking Mcp SOURCEpostking-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-bitsandtea-postking-mcp/storyline-confirm-brief.md

What storyline_confirm_brief does on Postking Mcp

AI agents use storyline_confirm_brief 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 storyline_confirm_brief is rated Medium

The 'confirm' action in a content/brand management context typically marks a brief as approved or locked in, creating or updating a workflow state. This is reversible (unlike Destructive) and doesn't execute arbitrary code (unlike Execute). While the empty description reduces confidence, the pattern of sibling tools and the 'brief' domain suggest Write-category behavior.

From the tool's definition Tool name 'storyline_confirm_brief' suggests confirmation/approval of a brief, which likely modifies state in a content management system.

Questions about storyline_confirm_brief

What does the storyline_confirm_brief tool do? +

storyline_confirm_brief is a write tool on the Postking MCP server. 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.

How do I enforce a policy on storyline_confirm_brief? +

Register the Postking MCP server in PolicyLayer and add a rule for storyline_confirm_brief: 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.

What risk level is storyline_confirm_brief? +

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

Can I rate-limit storyline_confirm_brief? +

Yes. Add a rate_limit block to the storyline_confirm_brief 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 storyline_confirm_brief completely? +

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

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Postking's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.