set_site_context

Store context about who is using the site and what it is for. This context is used by get_recommendations to tailor its output. Call this once during onboarding or whenever the context changes.

SERVERElementify MCP SOURCEvamerli/elementify-mcp

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/vamerli-elementify-mcp/set-site-context.md

WHAT IT DOES

What set_site_context does on Elementify MCP

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

RISK

Why set_site_context is rated Medium

An AI agent can call set_site_context faster than any human can review: one bad instruction and it creates or modifies resources in Elementify MCP by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set_site_context safely

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

set_site_context Rate-limited

set_site_context 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": {
    "set_site_context": {
      "limits": [
        {
          "counter": "set_site_context_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 Elementify MCP, apply this rule, and every set_site_context call is checked against it from then on.

FAQ

Questions about set_site_context

What does the set_site_context tool do? +

Store context about who is using the site and what it is for. This context is used by get_recommendations to tailor its output. Call this once during onboarding or whenever the context changes. It is categorised as a Write tool in the Elementify MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_site_context? +

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

What risk level is set_site_context? +

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

Can I rate-limit set_site_context? +

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

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

set_site_context is provided by the Elementify MCP server (vamerli/elementify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Elementify, and thousands of servers like it.

This server

All 254 Elementify 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 →