This record as markdown: /tools/io-github-bitsandtea-postking-mcp/storyline-get.md
What storyline_get does on Postking Mcp
AI agents call storyline_get to retrieve information from Postking Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why storyline_get is rated Low
The '_get' suffix strongly suggests this is a read operation that retrieves storyline data without side effects. Given the PostKing context (content management system), this likely queries existing storyline information for brands or posts. With no destructive, financial, or execution indicators, and no evidence of modification capability, this is classified as Read.
From the tool's definition Tool name 'storyline_get' follows RESTful convention for retrieval operations (get suffix indicates a fetch/query action). Description is empty, limiting direct confirmation.
Attacks that exploit this kind of access
The rule that runs storyline_get 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 storyline_get, this is the rule to start with:
storyline_get 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 Postking Mcp, apply this rule, and every storyline_get call is checked against it from then on.
Questions about storyline_get
storyline_get is a read tool on the Postking MCP server. It is categorised as a Read tool in the Postking Mcp MCP Server, which means it retrieves data without modifying state.
Register the Postking MCP server in PolicyLayer and add a rule for storyline_get: 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.
storyline_get 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 storyline_get 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 storyline_get. 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.
storyline_get 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