mmp_update
A write tool on the Pypi:dense Knowledge MCP server.
This record as markdown: /tools/dense-knowledge-mcp/mmp-update.md
What mmp_update does on Pypi:dense Knowledge
AI agents use mmp_update to create or update resources in Pypi:dense Knowledge, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pypi:dense Knowledge environment.
Why mmp_update is rated Medium
The tool modifies existing data within the knowledge store reversibly (fitting Write category). Severity is medium because the blast radius depends on what knowledge entries are updated—an agent could corrupt or mislead stored information, but the append-only architecture suggests this may be constrained.
From the tool's definition Tool name 'mmp_update' indicates modification of existing data. Server context describes 'append-only knowledge storage', and sibling tools include read (mmp_read, mmp_search), create (mmp_create), deprecate (mmp_deprecate), and list (mmp_list) operations.
Attacks that exploit this kind of access
The rule that runs mmp_update safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pypi:dense Knowledge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mmp_update, this is the rule to start with:
mmp_update 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 Pypi:dense Knowledge, apply this rule, and every mmp_update call is checked against it from then on.
Questions about mmp_update
mmp_update is a write tool on the Pypi:dense Knowledge MCP server. It is categorised as a Write tool in the Pypi:dense Knowledge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pypi:dense Knowledge MCP server in PolicyLayer and add a rule for mmp_update: 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 Pypi:dense Knowledge. Nothing to install.
mmp_update 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 mmp_update 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 mmp_update. 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.
mmp_update is provided by the Pypi:dense Knowledge MCP server (Lucky44k/dense-knowledge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pypi:dense Knowledge, and thousands of servers like it.
This server
Across the catalogue