Add a new blog to the mock API.
AI agents use add_blog to create or update resources in MCP Blog API — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Blog API environment.
This tool creates new blog posts, which is a reversible modification operation. It does not delete, destroy, or execute arbitrary code—the user can remove or edit the post later. The severity is medium because a malicious agent could spam blogs or inject malicious content, but the impact is limited to blog data and remains reversible. Confidence is high because the intent is explicit in both name and description.
From the tool's definition Tool name 'add_blog' and description 'Add a new blog to the mock API' indicate creation of new data records.
Attacks that exploit this kind of access
Add a new blog to the mock API. It is categorised as a Write tool in the MCP Blog API MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Blog API MCP server in PolicyLayer and add a rule for add_blog: 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 MCP Blog API. Nothing to install.
add_blog 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 add_blog 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 add_blog. 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.
add_blog is provided by the MCP Blog API MCP server (tussanakorn/poc_mcp_protocol_using_fastmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →