security_set
Privileged writer for reserved settings keys (security:* / policy:*) — the ONLY tool that can write them; the generic data_* tools refuse reserved keys. Upserts one key/value in the settings collection.
This record as markdown: /tools/2nd1st-open-mcp-apps/security-set.md
What security_set does on Open Mcp Apps
AI agents use security_set to create or update resources in Open Mcp Apps, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Open Mcp Apps environment.
Why security_set is rated Medium
This tool creates or modifies data reversibly by upserting security and policy settings. While it affects security-critical configuration keys, it does not delete data (which would be Destructive) nor execute arbitrary code (which would be Execute). It is a Write operation with elevated privileges over reserved namespaces.
From the tool's definition Tool description states it 'Privileged writer for reserved settings keys (security:* / policy:*)' and 'Upserts one key/value in the settings collection.' The terms 'writer' and 'upserts' indicate data modification capability.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs security_set safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Open Mcp Apps, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For security_set, this is the rule to start with:
security_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Open Mcp Apps, apply this rule, and every security_set call is checked against it from then on.
Questions about security_set
Privileged writer for reserved settings keys (security:* / policy:*) — the ONLY tool that can write them; the generic data_* tools refuse reserved keys. Upserts one key/value in the settings collection. It is categorised as a Write tool in the Open Mcp Apps MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Open Mcp Apps MCP server in PolicyLayer and add a rule for security_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 Open Mcp Apps. Nothing to install.
security_set 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 security_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.
Set action: deny in the PolicyLayer policy for security_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.
security_set is provided by the Open Mcp Apps MCP server (@2nd1st/open-mcp-apps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Open Mcp Apps, and thousands of servers like it.
This server
Across the catalogue