store_set

Store a key-value pair using the GLOBAL DataStoreService provider

SERVERFrontmcp SOURCEagentfront/frontmcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/frontmcp/store-set.md

WHAT IT DOES

What store_set does on Frontmcp

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

RISK

Why store_set is rated Medium

This tool writes data to a global data store, which is reversible (keys can be updated or cleared). It does not delete data irreversibly (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read). The 'GLOBAL' scope and lack of access controls visible in the description suggest moderate blast radius if an agent stores malicious or sensitive data, warranting medium severity.

From the tool's definition Tool description states 'Store a key-value pair using the GLOBAL DataStoreService provider' — the verb 'Store' indicates creation or modification of data in a persistent store.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs store_set safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For store_set, this is the rule to start with:

store_set Rate-limited

store_set 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": {
    "store_set": {
      "limits": [
        {
          "counter": "store_set_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every store_set call is checked against it from then on.

FAQ

Questions about store_set

What does the store_set tool do? +

Store a key-value pair using the GLOBAL DataStoreService provider. It is categorised as a Write tool in the Frontmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on store_set? +

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

What risk level is store_set? +

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

Can I rate-limit store_set? +

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

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

store_set is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Front, and thousands of servers like it.

This server

All 206 Front tools →

Across the catalogue

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →