fakestore_add_product · Fake Store API MCP Server MCP

WHAT IT DOES

What fakestore_add_product does on Fake Store API MCP Server

AI agents use fakestore_add_product to create or update resources in Fake Store API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fake Store API MCP Server environment.

WHY IT NEEDS A POLICY

Why fakestore_add_product needs a policy

This tool creates new data (a product), which is the defining characteristic of Write operations. Although the description notes the changes do not persist (limiting real-world impact), the operation itself is a create action. The low severity reflects that the tool operates on a demo/simulation system with no actual data durability, and misuse would only affect temporary session state rather than production data.

From the tool's definition Tool name contains 'add' and description states 'Add a new product to the store', which are write operations that create new data. The clarification '(simulation - does not persist)' indicates changes are temporary and reversible.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

fakestore_add_product Rate-limited

fakestore_add_product 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": {
    "fakestore_add_product": {
      "limits": [
        {
          "counter": "fakestore_add_product_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 Fake Store API MCP Server, so you can run agents against it safely.

FAQ

Questions about fakestore_add_product

What does the fakestore_add_product tool do? +

Add a new product to the store (simulation - does not persist). It is categorised as a Write tool in the Fake Store API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on fakestore_add_product? +

Register the Fake Store API MCP Server MCP server in PolicyLayer and add a rule for fakestore_add_product: 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 Fake Store API MCP Server. Nothing to install.

What risk level is fakestore_add_product? +

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

Can I rate-limit fakestore_add_product? +

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

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

fakestore_add_product is provided by the Fake Store API MCP Server MCP server (op-enny/mcp-server-fakestore). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.