Fetch project metadata from NISTA master registry
AI agents call fetch_nista_metadata to retrieve information from Project Management AI Analysis without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata from a registry with no indication of data modification, deletion, or code execution. The verb 'fetch' and the passive nature of querying a master registry for metadata clearly indicate a read-only operation. Severity is low as metadata retrieval typically has minimal blast radius and no irreversible effects.
From the tool's definition Tool name contains 'fetch' and description uses 'Fetch project metadata from NISTA master registry', which are read operations that retrieve data without modification.
Attacks that exploit this kind of access
Fetch project metadata from NISTA master registry. It is categorised as a Read tool in the Project Management AI Analysis MCP Server, which means it retrieves data without modifying state.
Register the Project Management AI Analysis MCP server in PolicyLayer and add a rule for fetch_nista_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 Project Management AI Analysis. Nothing to install.
fetch_nista_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 fetch_nista_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 fetch_nista_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.
fetch_nista_metadata is provided by the Project Management AI Analysis MCP server (pm-mcp-servers). 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 →