PerfDog 로그인 + csrf-token 자동 추출
AI agents invoke login to trigger actions in PerfDog to Tableau MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an authentication flow against an external service (PerfDog) and extracts security tokens. It is not a pure read operation because it initiates a session and harvests credentials/tokens, which constitutes an external operation with security implications. Misuse could result in unauthorized access or credential exposure.
From the tool's definition 'PerfDog 로그인 + csrf-token 자동 추출' — performs a login action and automatically extracts CSRF tokens, triggering an external authentication operation with side effects beyond simple data retrieval
Attacks that exploit this kind of access
PerfDog 로그인 + csrf-token 자동 추출. It is categorised as a Execute tool in the PerfDog to Tableau MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PerfDog to Tableau MCP Server MCP server in PolicyLayer and add a rule for login: 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 PerfDog to Tableau MCP Server. Nothing to install.
login is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the login 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 login. 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.
login is provided by the PerfDog to Tableau MCP Server MCP server (kimjeonghyun225-cpu/perfdog_mcp). 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 →