audit_property
Audit a FlowDot property — a deterministic, full-scope inspection of what it can DO and REACH — before recommending, installing, or running it. What you get back - Capability tags at a glance: \
This record as markdown: /tools/flowdot-llc-mcp-server/audit-property.md
What audit_property does on FlowDot MCP Server
AI agents call audit_property to retrieve information from FlowDot MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why audit_property is rated Low
This tool retrieves and analyzes metadata about a FlowDot property without making any changes, executing code, or triggering operations. It is a purely read-based inspection/auditing capability intended to provide information before actions are taken elsewhere. The low severity reflects minimal blast radius—incorrect audit results inform decisions but don't directly cause harm.
From the tool's definition Tool performs 'deterministic, full-scope inspection' and 'audit' of a property to determine what it can do and reach. Returns 'capability tags' for informational purposes. No modification, deletion, execution, or financial operations are performed.
Attacks that exploit this kind of access
The rule that runs audit_property safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FlowDot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For audit_property, this is the rule to start with:
audit_property is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every audit_property call is checked against it from then on.
Questions about audit_property
Audit a FlowDot property — a deterministic, full-scope inspection of what it can DO and REACH — before recommending, installing, or running it. What you get back - Capability tags at a glance: \. It is categorised as a Read tool in the FlowDot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for audit_property: 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 FlowDot MCP Server. Nothing to install.
audit_property 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 audit_property 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 audit_property. 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.
audit_property is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FlowDot MCP Server, and thousands of servers like it.
This server
Across the catalogue