store_get
Get a value from the GLOBAL DataStoreService provider
This record as markdown: /tools/frontmcp/store-get.md
What store_get does on Frontmcp
AI agents call store_get to retrieve information from Frontmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why store_get is rated Low
This tool retrieves data from a global data store without side effects. 'Get' operations are read-only queries that do not create, modify, delete, or execute external operations. The low severity reflects minimal blast radius—at worst, an agent could read sensitive cached values, but cannot alter state or trigger external effects.
From the tool's definition Tool name 'store_get' and description 'Get a value from the GLOBAL DataStoreService provider' indicate retrieval-only operation with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs store_get 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_get, this is the rule to start with:
store_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 Frontmcp, apply this rule, and every store_get call is checked against it from then on.
Questions about store_get
Get a value from the GLOBAL DataStoreService provider. It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.
Register the Front MCP server in PolicyLayer and add a rule for store_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 Frontmcp. Nothing to install.
store_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 store_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 store_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.
store_get 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.
More on Front, and thousands of servers like it.
This server
Across the catalogue