Medium Risk

database_standards

Get, set or delete database standards

How to control database_standards ↓

What database_standards does on MCP Project Standards Server

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

Medium Risk

Why database_standards needs a policy

The tool supports three operations: get (Read), set (Write), and delete (Destructive). Per the rules, the most severe applicable category must be chosen. 'Delete' implies irreversible removal of database standards, which elevates this to Destructive.

From the tool's definition 'Get, set or delete database standards'

Documented attack patterns abuse exactly the kind of access database_standards gives an agent:

How to control database_standards

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Project Standards Server, and nothing reaches the server without passing your rules. This is the rule we recommend for database_standards:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "database_standards": {
      "limits": [
        {
          "counter": "database_standards_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

database_standards 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.

  1. Create a free account and register MCP Project Standards Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about database_standards

What does the database_standards tool do? +

Get, set or delete database standards. It is categorised as a Write tool in the MCP Project Standards 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 database_standards? +

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

What risk level is database_standards? +

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

Can I rate-limit database_standards? +

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

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

database_standards is provided by the MCP Project Standards Server MCP server (liliangshan/mcp-server-project-standards). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Project Standards Server tool call.

Start from MCP Project Standards Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

11 MCP Project Standards Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.