Fetch all projects and their associated users, versions, categories, and tags from MantisBT and store them in the local metadata cache. Tags are fetched via the dedicated GET /tags endpoint when available. On installations where that endpoint is missing (MantisBT < 2.26), tags are collected by sc...
AI agents call sync_metadata to retrieve information from MantisBT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
sync_metadata is a read-only operation that retrieves metadata from the MantisBT server and populates a local cache. While it accesses multiple data types across projects, it performs no side effects on the source system—no data is created, modified, deleted, or irreversibly changed in MantisBT.
From the tool's definition Tool description states it "Fetch[es] all projects and their associated users, versions, categories, and tags" and "store[s] them in the local metadata cache." The operation is a retrieval and local caching of existing data with no modifications to the source…
Attacks that exploit this kind of access
Fetch all projects and their associated users, versions, categories, and tags from MantisBT and store them in the local metadata cache. Tags are fetched via the dedicated GET /tags endpoint when available. On installations where that endpoint is missing (MantisBT < 2.26), tags are collected by scanning all issues across all projects. This is useful for getting a complete overview of your MantisBT installation. The cache is valid for 24 hours by default (configurable via MANTIS_CACHE_TTL env var). Use this tool to refresh stale data. It is categorised as a Read tool in the MantisBT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MantisBT MCP Server MCP server in PolicyLayer and add a rule for sync_metadata: 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 MantisBT MCP Server. Nothing to install.
sync_metadata 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 sync_metadata 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 sync_metadata. 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.
sync_metadata is provided by the MantisBT MCP Server MCP server (@dpesch/mantisbt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →